Working with Amazon managed table buckets
Amazon managed table buckets are specialized S3 table buckets designed to store Amazon managed tables, such as
Accelerating data discovery with S3 Metadata journal and live
inventory tables. Unlike customer-managed table buckets that you create and manage directly,
Amazon managed table buckets are automatically provisioned by Amazon when you configure features that require Amazon
managed tables. When managed tables are created, they belong to a predefined namespace based on the source
bucket that can't be modified. Each Amazon account has one Amazon managed table bucket per Region, following the
naming convention aws-s3
. This bucket serves as a centralized location for all managed tables
associated with your account's resources in that Region.
The following table compares Amazon managed table buckets with customer-managed table buckets.
Feature | Amazon managed table buckets | Customer-managed table buckets |
---|---|---|
Creation | Automatically created by Amazon services | You create these manually |
Naming | Use a standard naming convention (aws-s3) | You define your own names |
Table creation | Only Amazon services can create tables | You can create tables |
Namespace control | You can't create or delete namespaces (All tables belong to a fixed namespace) | You can create and delete namespaces |
Access | Read-only access | Full access |
Encryption | You can only change the default encryption (SSE-S3) settings if you encrypted the initial table with a customer manged Amazon KMS key. | You can set bucket-level default encryption and modify it anytime |
Maintenance | Managed by Amazon services | Automated maintenance can be customized at bucket level |
Permissions to create Amazon managed table buckets
To work with Amazon managed table buckets, you need permissions to create Amazon managed table buckets and tables, specify encryption settings for Amazon managed tables as well as basic read permissions for querying tables.
The following is an example policy that will allow you to create an Amazon managed table bucket through service configurations:
{ "Version":"2012-10-17", "Statement":[ { "Sid":"PermissionsToWorkWithMetadataTables", "Effect":"Allow", "Action":[ "s3:CreateBucketMetadataTableConfiguration", "s3tables:CreateTableBucket", "s3tables:CreateNamespace", "s3tables:CreateTable", "s3tables:GetTable", "s3tables:PutTablePolicy" "s3tables:PutTableEncryption", "kms:DescribeKey" ], "Resource":[ "arn:aws:s3:::bucket/
amzn-s3-demo-source-bucket
", "arn:aws:s3tables:region
:111122223333
:bucket/aws-s3", "arn:aws:s3tables:region
:111122223333
:bucket/aws-s3/table/*" ] } ] }
The following is an example policy that will allow you to query tables in Amazon managed table buckets:
{ "Version":"2012-10-17", "Statement":[ { "Sid":"PermissionsToWorkWithMetadataTables", "Effect":"Allow", "Action":[ "s3tables:GetTable", "s3tables:GetTableData", "s3tables:GetTableMetadataLocation", "kms:Decrypt" ], "Resource":[ "arn:aws:s3tables:
region
:111122223333
:bucket/aws-s3", "arn:aws:s3tables:region
:111122223333
:bucket/aws-s3/table/*" ] } ] }
Querying tables in Amazon managed table buckets
You can query Amazon managed tables in Amazon managed table buckets using access methods and engines supported by S3 Tables. The following are some example queries
Encryption for Amazon managed table buckets
By default, Amazon managed table buckets are encrypted with server-side encryption using Amazon S3 managed keys (SSE-S3). After your Amazon managed table bucket is created, you can use PutTableBucketEncryption to set the bucket's default encryption setting to use server-side encryption with Amazon Key Management Service (Amazon KMS) keys (SSE-KMS).
During creation of your Amazon managed tables, you can choose to encrypt them with SSE-KMS. If you choose to use SSE-KMS, you must provide a customer managed KMS key in the same Region as your Amazon managed table bucket. You can set the encryption type for your Amazon managed tables only during table creation. After an Amazon managed table is created, you can't change its encryption setting.
If you want the Amazon managed table bucket and the tables stored in it to use the same KMS key, make sure to use the same KMS key that you used to encrypt your tables to encrypt your table bucket after it's been created. After you've changed the default encryption settings for your table bucket to use SSE-KMS, those encryption settings are used for any future tables that are created in the bucket.