S3 bucket data migration to S3 table

0

i have run solution given at link- https://github.com/aws-solutions-library-samples/guidance-for-migrating-tabular-data-from-amazon-s3-to-s3-tables/tree/main, to move data files from my S3 bucket to S3 tables. i already have glue database and glue table for my S3 bucket, and in S3 table bucket i already have a database isnide that table bucket, now after executing the step function i get below error while querying the table in athena which is created under my S3 table bucket.,

error- GENERIC_INTERNAL_ERROR: Get table request failed: com.amazonaws.services.glue.model.ValidationException: Unsupported Federation Resource - Invalid table or column names. (Service: AWSGlue; Status Code: 400; Error Code: ValidationException; Request ID: 5751b21a-dafb-410f-a40c-765cff4a48f2; Proxy: null) This query ran against the "fdp_test_ns" database, unless qualified by the query. Please post the error message on our forum or contact customer support with Query Id:

asked 2 months ago113 views
1 Answer
0

The error you're encountering is likely due to the use of uppercase letters in your table name or column names when creating the S3 table. When working with S3 Tables, it's crucial to use all lowercase letters for table names and column definitions to ensure compatibility with AWS Lake Formation and the AWS Glue Data Catalog.

To resolve this issue, you should check the following:

  1. Verify that your table name is in all lowercase.
  2. Ensure all column names in your table definition are in lowercase.
  3. If you find any uppercase letters, you'll need to recreate the table with the correct lowercase naming.

This requirement is specific to S3 Tables and is necessary for the table to be properly supported by AWS Lake Formation and the AWS Glue Data Catalog. If your table name or definition contains any capital letters, it won't be visible to AWS analytics services like Amazon Athena, even if your table buckets are integrated with these services.

To fix this, you'll need to:

  1. Review your table creation process, ensuring all names are in lowercase.
  2. If necessary, drop the existing table.
  3. Recreate the table using all lowercase letters for the table name and column names.

After making these changes, you should be able to query your S3 table in Athena without encountering the "Unsupported Federation Resource" error. Remember, this applies to both the table name and all column names in your table definition.
Sources
Tutorial: Getting started with S3 Tables - Amazon Simple Storage Service
Creating an Amazon S3 table - Amazon Simple Storage Service

profile picture
answered 2 months ago
AWS
SUPPORT ENGINEER
reviewed 2 months ago
  • I have checked my table and column names are valid. If i select my S3 table catalog and database , then i dont see this tablr in athena, but i see the table in S3 table bucket from the console, so i dont know why this table doesnt appear in athena

  • Hi @ashish, if you cannot see the table in Athena but verified it exists through the Console, you may be want to check that you have enabled S3 Tables integration with AWS analytics services.

  • i am able to see the table in athena now but i get below error while running the query- Insufficient permissions to execute the query. Principal does not have any privilege on specified resource This query ran against the "fdp_test_ns" database, unless qualified by the query. Please post the error message on our forum or contact customer support with Query Id:

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions