ErrorDetails
If the CreateBucketMetadataTableConfiguration request succeeds, but S3 Metadata was
unable to create the table, this structure contains the error code and error message.
Contents
- ErrorCode
-
If the
CreateBucketMetadataTableConfigurationrequest succeeds, but S3 Metadata was unable to create the table, this structure contains the error code. The possible error codes and error messages are as follows:-
AccessDeniedCreatingResources- You don't have sufficient permissions to create the required resources. Make sure that you haves3tables:CreateNamespace,s3tables:CreateTable,s3tables:GetTableands3tables:PutTablePolicypermissions, and then try again. To create a new metadata table, you must delete the metadata configuration for this bucket, and then create a new metadata configuration. -
AccessDeniedWritingToTable- Unable to write to the metadata table because of missing resource permissions. To fix the resource policy, Amazon S3 needs to create a new metadata table. To create a new metadata table, you must delete the metadata configuration for this bucket, and then create a new metadata configuration. -
DestinationTableNotFound- The destination table doesn't exist. To create a new metadata table, you must delete the metadata configuration for this bucket, and then create a new metadata configuration. -
ServerInternalError- An internal error has occurred. To create a new metadata table, you must delete the metadata configuration for this bucket, and then create a new metadata configuration. -
TableAlreadyExists- The table that you specified already exists in the table bucket's namespace. Specify a different table name. To create a new metadata table, you must delete the metadata configuration for this bucket, and then create a new metadata configuration. -
TableBucketNotFound- The table bucket that you specified doesn't exist in this AWS Region and account. Create or choose a different table bucket. To create a new metadata table, you must delete the metadata configuration for this bucket, and then create a new metadata configuration.
Type: String
Required: No
-
- ErrorMessage
-
If the
CreateBucketMetadataTableConfigurationrequest succeeds, but S3 Metadata was unable to create the table, this structure contains the error message. The possible error codes and error messages are as follows:-
AccessDeniedCreatingResources- You don't have sufficient permissions to create the required resources. Make sure that you haves3tables:CreateNamespace,s3tables:CreateTable,s3tables:GetTableands3tables:PutTablePolicypermissions, and then try again. To create a new metadata table, you must delete the metadata configuration for this bucket, and then create a new metadata configuration. -
AccessDeniedWritingToTable- Unable to write to the metadata table because of missing resource permissions. To fix the resource policy, Amazon S3 needs to create a new metadata table. To create a new metadata table, you must delete the metadata configuration for this bucket, and then create a new metadata configuration. -
DestinationTableNotFound- The destination table doesn't exist. To create a new metadata table, you must delete the metadata configuration for this bucket, and then create a new metadata configuration. -
ServerInternalError- An internal error has occurred. To create a new metadata table, you must delete the metadata configuration for this bucket, and then create a new metadata configuration. -
TableAlreadyExists- The table that you specified already exists in the table bucket's namespace. Specify a different table name. To create a new metadata table, you must delete the metadata configuration for this bucket, and then create a new metadata configuration. -
TableBucketNotFound- The table bucket that you specified doesn't exist in this AWS Region and account. Create or choose a different table bucket. To create a new metadata table, you must delete the metadata configuration for this bucket, and then create a new metadata configuration.
Type: String
Required: No
-
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following:
