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

Airbyte

<@U04S8PLJWMT> how to use the dynamodb source connector to read a dynamodb table in another aws account?

Unfortunately, *cross-account DynamoDB access is a known open issue with the Airbyte `source-dynamodb` connector* and is not currently supported out of the box.

 Why It Doesn't Work The connector's `check` and `discover` phases call the <https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_ListTables.html|ListTables API>, which only returns tables from the *current* AWS account. When using role-based access (where Airbyte runs in Account A but the tables are in Account B), the connector attempts to list tables in Account A — not Account B — causing an authorization error like: [<https://github.com/airbytehq/airbyte/issues/60944|GitHub Issue>]

```User: arn:aws:sts::account_A:assumed-role/AccountARole/... is not authorized to perform:
dynamodb:ListTables on resource: arn:aws:dynamodb:...:account_A:table/*
because no identity-based policy allows the dynamodb:ListTables action```
 Current Role-Based Access Behavior The connector supports role-based access by omitting `access_key_id` and `secret_access_key` from the configuration. In that case, it uses `DefaultCredentialsProvider`, which picks up the IAM role of the underlying container workload: [<https://docs.airbyte.com/integrations/sources/dynamodb|DynamoDB Docs>]

> Role based access can be achieved by omitting both values from the configuration. The connector will then use `DefaultCredentialsProvider` which will use the underlying role executing the container workload in AWS.
However, this mechanism does *not* support cross-account scenarios because the `ListTables` call is scoped to the account associated with the assumed role's context, not the target account. [<https://github.com/airbytehq/airbyte/issues/60944|GitHub Issue>]

 What Has Been Proposed (But Not Merged) A community contributor has proposed a draft fix using STS authentication to properly assume a cross-account role, but it has not been cleaned up or merged into the Airbyte codebase yet. [<https://github.com/airbytehq/airbyte/issues/60944|GitHub Issue>]

 Summary There is *no officially supported workaround* in the current connector for cross-account DynamoDB access. The issue remains open. If this is critical for your use case, you may want to:

1. *Follow or contribute to the open GitHub issue* (<https://github.com/airbytehq/airbyte/issues/60944|#60944>).
2. Consider whether you can grant the necessary `dynamodb:ListTables` permission on Account A's role scoped to Account B's resources as a temporary measure, though the `ListTables` API limitation (it only returns tables in the current account) means this may not fully resolve the issue. :thumbsup: 0 button :thumbsdown: 0 button :information_source: *Tip:* Mention *@kapa.ai* in the thread for follow-ups or *DM the app* for *1-to-1* help.