AWS AmazonS3 documentation change
Summary
Added important note requiring lowercase letters in table/column names for AWS service compatibility
Security assessment
Change addresses compatibility requirements with AWS analytics services, not security. The warning prevents configuration errors but doesn't mitigate vulnerabilities or describe security controls.
Diff
diff --git a/AmazonS3/latest/userguide/s3-tables-buckets-naming.md b/AmazonS3/latest/userguide/s3-tables-buckets-naming.md index 5302a0a7f..5bf7c4e61 100644 --- a//AmazonS3/latest/userguide/s3-tables-buckets-naming.md +++ b//AmazonS3/latest/userguide/s3-tables-buckets-naming.md @@ -79,0 +80,6 @@ The following naming rules apply to tables and namespaces within table buckets: +###### 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."`** +