AWS Security ChangesHomeSearch

AWS AmazonS3 documentation change

Service: AmazonS3 · 2025-08-16 · Documentation low

File: AmazonS3/latest/userguide/s3-tables-integrating-athena.md

Summary

Added compatibility warning about lowercase requirements for table definitions when using Athena

Security assessment

Documentation update focuses on preventing integration errors with AWS analytics services. No security implications are mentioned or implied in the change.

Diff

diff --git a/AmazonS3/latest/userguide/s3-tables-integrating-athena.md b/AmazonS3/latest/userguide/s3-tables-integrating-athena.md
index a5c5f0d4b..601485890 100644
--- a//AmazonS3/latest/userguide/s3-tables-integrating-athena.md
+++ b//AmazonS3/latest/userguide/s3-tables-integrating-athena.md
@@ -12,0 +13,6 @@ You can also run queries in Athena from the Amazon S3 console.
+###### Important
+
+When creating tables, make sure that you use all lowercase letters in your table names and table definitions. For example, make sure that your column names are all lowercase. If your table name or table definition contains capital letters, the table isn't supported by AWS Lake Formation or the AWS Glue Data Catalog. In this case, your table won't be visible to AWS analytics services such as Amazon Athena, even if your table buckets are integrated with AWS analytics services. 
+
+If your table definition contains capital letters, you receive the following error message when running a `SELECT` query in Athena: **`"GENERIC_INTERNAL_ERROR: Get table request failed: com.amazonaws.services.glue.model.ValidationException: Unsupported Federation Resource - Invalid table or column names."`**
+