Closed murat-cetinkaya closed 6 months ago
@itaseskii I hope the description of the issue is clear. Please let me know if you have further question.
To clarify - should we not be doing a SACN in our code, or is SCAN the right operation to be using, and we need to update our docs to require this permission?
@evantahler scan is the right operation to perform since you need to read from all the partitions for a given table. What the connector needs to take into account is that it might not have a read access to some of the tables that are retrieved with https://docs.aws.amazon.com/cli/latest/reference/dynamodb/list-tables.html. The most straightforward way to handle this is to catch the exception and ignore the table on discover() and read(). We can also consider adding a configuration property for this and making it opt-in.
Connector Name
DynamoDB Source
Connector Version
0.1.2
What step the error happened?
Configuring a new connector
Revelant information
I'm facing a problem with the Airbyte DynamoDB Source connector. I have an issue with Airbyte DynamoDB Source connector. I have 10 DynamoDB tables in my account. I created an AWS user with scan, read permissions to read from a single DynamoDB table using the below policy:
Despite these settings, the connector asks SCAN permission for the other tables on the creation of a connection and I get the following error:
ERROR i.a.i.b.AirbyteExceptionHandler(uncaughtException):26 Something went wrong in the connector. See the logs for more details. software.amazon.awssdk.services.dynamodb.model.DynamoDbException: User: arn:aws:iam::account-id:user/airbyte_user is not authorized to perform: dynamodb:Scan on resource: arn:aws:dynamodb:us-west-1:account-id:table/another_table because no identity-based policy allows the dynamodb:Scan action (Service: DynamoDb, Status Code: 400, Request ID: A8RC5JQ2FUQRHR5M368RPUKR5RVV4KQNSO5AEMVJF66Q9AAJG)
Relevant log output
Contribute