AWS Security ChangesHomeSearch

AWS AmazonS3 documentation change

Service: AmazonS3 · 2025-08-19 · Documentation medium

File: AmazonS3/latest/userguide/s3-tables-create.md

Summary

Updated documentation links to correct references for Lake Formation permissions and error resolution steps. Fixed broken hyperlinks and clarified paths to permission-granting documentation.

Security assessment

The changes primarily correct documentation links related to Lake Formation permissions. While permissions management is a security concern, there is no explicit evidence of a security vulnerability being patched. The updates improve clarity for users to properly configure access controls, reducing misconfiguration risks.

Diff

diff --git a/AmazonS3/latest/userguide/s3-tables-create.md b/AmazonS3/latest/userguide/s3-tables-create.md
index 8fccb32a9..704f9b64e 100644
--- a//AmazonS3/latest/userguide/s3-tables-create.md
+++ b//AmazonS3/latest/userguide/s3-tables-create.md
@@ -50 +50 @@ If your table definition contains capital letters, you receive the following err
-The following procedure uses the Amazon S3 console to create a table with Amazon Athena. If you haven't already created a namespace in your table bucket, you can do so as part of this process. Before performing the following steps, make sure that you've integrated your table buckets with AWS analytics services in this Region. For more information, see [Using Amazon S3 Tables with AWS analytics services](./s3-tables-integrating-aws.html).
+The following procedure uses the Amazon S3 console to create a table with Amazon Athena. If you haven't already created a namespace in your table bucket, you can do so as part of this process. Before performing the following steps, make sure that you've integrated your table buckets with AWS analytics services in this Region. For more information, see [](./.html#s3-tables-integrating-aws).
@@ -80 +80 @@ When you create a table using Athena that table inherits the default encryption
-If you don't see these values in the **Catalog** and **Database** fields, make sure that you've integrated your table buckets with AWS analytics services in this Region. For more information, see [Using Amazon S3 Tables with AWS analytics services](./s3-tables-integrating-aws.html). 
+If you don't see these values in the **Catalog** and **Database** fields, make sure that you've integrated your table buckets with AWS analytics services in this Region. For more information, see [](./.html#s3-tables-integrating-aws). 
@@ -88 +88 @@ If you don't see these values in the **Catalog** and **Database** fields, make s
-     * If you receive the error **`"Insufficient permissions to execute the query. Principal does not have any privilege on specified resource"`** when you try to run a query in Athena, you must be granted the necessary Lake Formation permissions on the table. For more information, see [Granting permission on a table or database](./s3-tables-integrating-aws.html#grant-lf-table). 
+     * If you receive the error **`"Insufficient permissions to execute the query. Principal does not have any privilege on specified resource"`** when you try to run a query in Athena, you must be granted the necessary Lake Formation permissions on the table. For more information, see [Granting Lake Formation permission on a table or database](./grant-permissions-tables.html#grant-lf-table). 
@@ -90 +90 @@ If you don't see these values in the **Catalog** and **Database** fields, make s
-     * If you receive the error **`"Iceberg cannot access the requested resource"`** when you try to run a query in Athena, go to the AWS Lake Formation console and make sure that you've granted yourself permissions on the table bucket catalog and database (namespace) that you created. Don't specify a table when granting these permissions. For more information, see [Granting permission on a table or database](./s3-tables-integrating-aws.html#grant-lf-table). 
+     * If you receive the error **`"Iceberg cannot access the requested resource"`** when you try to run a query in Athena, go to the AWS Lake Formation console and make sure that you've granted yourself permissions on the table bucket catalog and database (namespace) that you created. Don't specify a table when granting these permissions. For more information, see [Granting Lake Formation permission on a table or database](./grant-permissions-tables.html#grant-lf-table).