Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

<@U04SE163WC8> how to configure `AWS_ASSUME_ROLE_EXTERNAL_ID` variable? I am running Airbyte OSS 0.63.13, configured through docker

To configure the `AWS_ASSUME_ROLE_EXTERNAL_ID` variable, you would typically set it as an environment variable. However, based on the provided knowledge sources, it seems that the IAM role authentication feature is not yet fully supported in the open-source version of Airbyte.   In the [Github issue](<https://github.com/airbytehq/airbyte/issues/34582>) discussing the S3 source connection via IAM role, users reported issues with the `AWS_ASSUME_ROLE_EXTERNAL_ID` not being passed to the `source-s3` container. The issue is still open and it seems that the feature is currently being focused on for Airbyte Cloud users, with exploration for self-hosted users to come later.  In the [Github issue](<https://github.com/airbytehq/airbyte/issues/33039>) discussing the Redshift destination connection via IAM role, a contributor mentioned that they are currently focused on enabling this feature for users of Airbyte Cloud and will later explore if/how they want to enable this for self-hosted users.  For general configuration of Airbyte, you can modify the bundled `.env` file in the Airbyte Docker deployment as mentioned in the [Configuring Airbyte documentation](<https://docs.airbyte.com/operator-guides/configuring-airbyte>). However, please note that this might not resolve the IAM role authentication issue as it seems to be a feature in development.  I recommend keeping an eye on the mentioned Github issues for updates on the feature's availability for the open-source version of Airbyte.

<@U04SE163WC8> I believe I saw another recent GH issue that confirmed this functionality. Please explain the process on how to set up this env variable. Do I need to stop and run the docker containers? Do I need to set this up within any docker container or in the OS on top of the container?

To set up an environment variable for a Docker container, you would typically add it to the `.env` file or directly in the `docker-compose.yaml` file. Here's a general process:  1. Open the `.env` file in the root directory of your Airbyte deployment. 2. Add a new line with the environment variable you want to set, like so: `AWS_ASSUME_ROLE_EXTERNAL_ID=your_value` 3. Save and close the `.env` file.  After setting the environment variable, you would need to restart your Docker containers for the changes to take effect. You can do this by running the following commands:  ```bash docker-compose down docker-compose up ```  The first command stops the running containers, and the second command starts them again with the new environment variable.  However, as mentioned in my previous message, the IAM role authentication feature, which involves the `AWS_ASSUME_ROLE_EXTERNAL_ID` variable, is not fully supported in the open-source version of Airbyte according to the provided knowledge sources. While you can set the environment variable as described, it might not resolve any issues related to IAM role authentication.  For more information on configuring Airbyte, you can refer to the [Configuring Airbyte documentation](<https://docs.airbyte.com/operator-guides/configuring-airbyte>). For updates on the IAM role authentication feature, I recommend following the relevant [Github issues](<https://github.com/airbytehq/airbyte/issues/34582>).