S3 Connector Issue with AWS_ASSUME_ROLE_EXTERNAL_ID Environment Variable

Summary

The user is facing an issue with the S3 connector after updating Airbyte to be used with abctl and Docker on an EC2 instance. The error message requests the definition of the AWS_ASSUME_ROLE_EXTERNAL_ID environment variable. The user is seeking guidance on how to achieve this with the specific stack of EC2, abctl, Docker, and Kubernetes.


Question

Hello there ! I just updated airbyte to be used with abctl and docker on a EC2 instance. My S3 connector does not work anymore, it asks me to define a AWS_ASSUME_ROLE_EXTERNAL_ID environnement variable : how can I achieve this with this specific stack ? (ec2 => abctl => docker => kubernetes)



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["s3-connector", "aws-assume-role-external-id", "ec2", "abctl", "docker", "kubernetes"]

IAM auth for this is listed in the https://docs.airbyte.com/integrations/sources/s3#option-2-using-an-iam-role-most-secure|docs as not being supported in OSS:
> NOTE
> S3 authentication using an IAM role member is not supported using the OSS platform.
There is a GitHub issue related to this here as well:
https://github.com/airbytehq/airbyte/issues/34582

In theory this should be possible if the extraEnv set on the workloads propagates to the action sync worker, but I’m assuming there’s some reason that isn’t happening currently that is more involved.

<@U07U0QP8G3V> do you use source or destination connector for S3?

<@U035912NS77> maybe instance profile for EC2 is an option here?
https://airbytehq.slack.com/archives/C021JANJ6TY/p1728082396338529?thread_ts=1727868326.601819&cid=C021JANJ6TY

Hello,
Thanks for your replies, I was (and am) on a instance profile before upgrading, but it didn’t work (since the extra layers of networking due to the use of kube)
I followed the steps and set http_put_response_hop_limit to 3 and it solved this issue. Thanks for your help ! :slightly_smiling_face:

Hi <@U07U0QP8G3V> great to hear it works for you.

Can you help me on where this needs to be configured? http_put_response_hop_limit

<@U0606G3NKU4> check this thread https://airbytehq.slack.com/archives/C021JANJ6TY/p1728082396338529?thread_ts=1727868326.601819&amp;cid=C021JANJ6TY

I’ll try that out. Thanks for sharing it here <@U05JENRCF7C> :raised_hands:

This worked thanks <@U05JENRCF7C> :handshake: