[FEATURE] Feature request: I want to filter DynamoDB tables into Athena

[vaquarkhan]

Is your feature request related to a problem? If yes, please describe. Yes User want control to display only selected tables into Athena .

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

User has multiple teams and tables also contain KMS key few are configured via Lake formation , now I can see following issues.

• Asking permission for KMS key which own by other team is big issue as they are not comfortable to share this keys and since I have my 4 -5 tables which I want to use in Athena blocked by others team.
• Without keys Athena connector will give error and cannot fetch any tables , so as per current functionality either all or non tables can fetch using connector.
• Same issue we have with Lake formation
• User want to display only few logs table in quicksight and since Dynamodb has no direct connectivity want to use only few logs table via Athena to display in Quicksight.

Describe the solution you'd like A clear and concise description of what you want to happen. Want a filter where i can configure my tables which will display in Athena,

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

I have fixed code in following branch , raising pull request please review . https://github.com/vaquarkhan/aws-athena-query-federation/tree/master/athena-dynamodb

Additional context Add any other context or screenshots about the feature request here.

I have tested all possible scenario in committed code.

I have no expertise in cloud formation so i am adding Lambda parameter manually if you could add into your template cloud formation would be great help

[vaquarkhan]

Pull request for review

• https://github.com/awslabs/aws-athena-query-federation/pull/607

[chngpe]

Hi

Thank you for reaching out.

Asking permission for KMS key which own by other team is big issue as they are not comfortable to share this keys and since I have my 4 -5 tables which I want to use in Athena blocked by others team.

We decide to approach this differently, rather than customer has to provide filter to filter out the table, we decide to skip table when customer doesn't have access to the encrypted table in dynamoDB.

We have added support in our latest version of connector to skip the dynamoDB table for kms encrypted table when lambda role doesn't have sufficient permission to access KMS key.

Closing ticket, if you have additional questions feel free to reopen this.