How do i set up external id

AWS_ASSUME_ROLE_EXTERNAL_ID

in locally deployed instance

Based on the information provided in the knowledge sources, I'm afraid I don't have enough information to give you a complete answer on how to set up the

AWS_ASSUME_ROLE_EXTERNAL_ID

for a locally deployed Airbyte instance. However, I can provide some relevant context: 1. The IAM role authentication feature, which uses the

AWS_ASSUME_ROLE_EXTERNAL_ID

, is not supported in the open-source (OSS) version of Airbyte. This feature is only available for users in a Sales Assist workflow, as mentioned in the [S3 source documentation](https://docs.airbyte.com/integrations/sources/s3#option-2-using-an-iam-role-most-secure): "S3 authentication using an IAM role member is not supported using the OSS platform. S3 authentication using an IAM role member must be enabled by a member of the Airbyte team." 2. There are ongoing discussions and issues related to this feature in the open-source community. For example, in a [GitHub issue](https://github.com/airbytehq/airbyte/issues/34582), users have reported that the

AWS_ASSUME_ROLE_EXTERNAL_ID

is not being passed to the

source-s3

container in local deployments. 3. For locally deployed instances, the current recommendation is to use IAM user credentials (Access Key ID and Secret Access Key) instead of IAM roles. You can find instructions for setting up IAM user authentication in the [S3 source documentation](https://docs.airbyte.com/integrations/sources/s3#option-1-using-an-iam-user). If you need to use IAM role authentication with external ID for a locally deployed instance, you may need to contact Airbyte's sales team for more information or consider using their managed service where this feature is supported.