When I spin up Airbyte using abctl in an ec2 with an instance profile, the s3 connector isn’t using the iam role of the ec2, throws a “no authentication method” error

Based on the knowledge sources, there are known issues with S3 connector authentication using IAM roles, particularly when running Airbyte outside of AWS or with instance profiles. ## The Issue When using the S3 connector with an EC2 instance profile, the connector may not automatically use the IAM role credentials from the instance. This is a documented limitation, as mentioned in [this GitHub issue](https://github.com/airbytehq/airbyte/issues/57577), where a user running Airbyte OSS on GKE encountered the same "Unable to locate credentials" error when trying to use role-based authentication. ## Current Limitations According to the [S3 source documentation](https://docs.airbyte.com/integrations/sources/s3#step-1-set-up-s3), IAM Role authentication for S3 sources is not supported in the OSS platform: > "S3 authentication using an IAM role member is not supported using the OSS platform." Similarly, for S3 destinations, the [documentation states](https://docs.airbyte.com/integrations/destinations/s3#authentication-option-1-using-an-iam-role-most-secure) that IAM role authentication must be enabled by the Airbyte team. ## Workaround The recommended approach for OSS deployments is to use IAM User credentials (Access Key ID and Secret Access Key) instead of relying on the instance profile. According to the [S3 destination setup guide](https://docs.airbyte.com/integrations/destinations/s3#step-2-set-up-the-s3-destination-connector-in-airbyte): - Create an Airbyte-specific IAM user with read/write permissions to your S3 bucket - Generate Access Key ID and Secret Access Key for this user - Provide these credentials when configuring the S3 connector ## Potential Solution There is [an open pull request](https://github.com/airbytehq/airbyte/issues/34582) addressing this issue. One user mentioned creating a PR to allow passing credentials properly for role assumption, which you could potentially build and use if you're self-hosting. If you need to use IAM roles, you may need to contact the Airbyte Sales team for Enterprise features, or consider using explicit AWS credentials as a workaround.