1 Answer
- Newest
- Most votes
- Most comments
1
The issue you’re facing is likely due to the fact that the existing tables in your Glue catalog were created before the KMS key was changed. These tables are still associated with the old key, and that’s why you’re unable to query them from the consumer account.
Unfortunately, AWS Glue doesn’t provide a built-in way to re-encrypt the metadata of existing tables with a new key. The metadata encryption is determined at the time of table creation and can’t be changed afterwards.
So either you recreate the Tables or use AWS Glue Data Catalog Client
Relevant content
- asked a year ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
thanks for answering. what do you mean by 'use AWS Glue Data Catalog Client' ? how it can help?
The AWS Glue Data Catalog client can be used to manage the metadata of your data stored in Amazon S3. It provides a unified metadata repository across various services, enabling you to query your data across data stores.
In the context of your issue, you could use the AWS Glue Data Catalog client to programmatically recreate the tables. This would involve dropping the existing tables and creating new ones, which would then be encrypted with the new key. Here's a high-level overview of how you might do this: