We recommend that you retrieve your S3 Metadata configurations by using the V2
GetBucketMetadataTableConfiguration API operation. We no longer recommend using the V1
GetBucketMetadataTableConfiguration API operation.
If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete
and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create
a live inventory table.
You can use the V2 GetBucketMetadataConfiguration API operation with V1 or V2
metadata table configurations. However, if you try to use the V1
GetBucketMetadataTableConfiguration API operation with V2 configurations, you
will receive an HTTP 405 Method Not Allowed error.
Make sure that you update your processes to use the new V2 API operations
(CreateBucketMetadataConfiguration, GetBucketMetadataConfiguration, and
DeleteBucketMetadataConfiguration) instead of the V1 API operations.
You must URL encode any signed header values that contain spaces. For example, if your header value is my file.txt, containing two spaces after my, you must URL encode this value to my%20%20file.txt.
Example
Use a bare-bones client and the command you need to make an API call.
We recommend that you retrieve your S3 Metadata configurations by using the V2 GetBucketMetadataTableConfiguration API operation. We no longer recommend using the V1
GetBucketMetadataTableConfigurationAPI operation.If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete and re-create your configuration by using CreateBucketMetadataConfiguration so that you can expire journal table records and create a live inventory table.
Retrieves the V1 S3 Metadata configuration for a general purpose bucket. For more information, see Accelerating data discovery with S3 Metadata in the Amazon S3 User Guide.
You can use the V2
GetBucketMetadataConfigurationAPI operation with V1 or V2 metadata table configurations. However, if you try to use the V1GetBucketMetadataTableConfigurationAPI operation with V2 configurations, you will receive an HTTP405 Method Not Allowederror.Make sure that you update your processes to use the new V2 API operations (
CreateBucketMetadataConfiguration,GetBucketMetadataConfiguration, andDeleteBucketMetadataConfiguration) instead of the V1 API operations.To use this operation, you must have the
s3:GetBucketMetadataTableConfigurationpermission. For more information, see Setting up permissions for configuring metadata tables in the Amazon S3 User Guide.The following operations are related to
GetBucketMetadataTableConfiguration:CreateBucketMetadataTableConfiguration
DeleteBucketMetadataTableConfiguration
You must URL encode any signed header values that contain spaces. For example, if your header value is
my file.txt, containing two spaces aftermy, you must URL encode this value tomy%20%20file.txt.Example
Use a bare-bones client and the command you need to make an API call.
Param: GetBucketMetadataTableConfigurationCommandInput
GetBucketMetadataTableConfigurationCommandInput
Returns
GetBucketMetadataTableConfigurationCommandOutput
See
inputshape.responseshape.configshape.Throws
S3ServiceException
Base exception class for all service exceptions from S3 service.