AWS AmazonS3 documentation change
Summary
Updated documentation links to point to correct anchor references and separate permissions guide
Security assessment
The changes primarily fix broken links and reorganize documentation references. While they mention Lake Formation permissions in error resolution steps, this is existing security guidance being properly linked rather than new security content. No specific vulnerability or new security feature is introduced.
Diff
diff --git a/AmazonS3/latest/userguide/s3-tables-integrating-athena.md b/AmazonS3/latest/userguide/s3-tables-integrating-athena.md index 601485890..cf33349b0 100644 --- a//AmazonS3/latest/userguide/s3-tables-integrating-athena.md +++ b//AmazonS3/latest/userguide/s3-tables-integrating-athena.md @@ -23 +23 @@ The following procedure uses the Amazon S3 console to access the Athena query ed -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). +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). @@ -43 +43 @@ In the query editor, the **Catalog** field should be populated with **s3tablesca -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). @@ -49 +49 @@ 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). @@ -51 +51 @@ 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 the query, 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 the query, 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).