AWS lake-formation documentation change
Summary
Minor text formatting changes (capitalization of 'Tables', rephrasing)
Security assessment
These changes involve capitalization corrections and grammatical improvements without altering security-related content or introducing new security considerations.
Diff
diff --git a/lake-formation/latest/dg/notes-s3-catalog.md b/lake-formation/latest/dg/notes-s3-catalog.md index 81c690fdc..cffc182e6 100644 --- a//lake-formation/latest/dg/notes-s3-catalog.md +++ b//lake-formation/latest/dg/notes-s3-catalog.md @@ -5 +5 @@ -# S3 tables catalog integration limitations +# S3 Tables catalog integration limitations @@ -7 +7 @@ -You can integrate Amazon S3 table buckets and tables with AWS Glue Data Catalog (Data Catalog), and register the catalog as a Lake Formation data location from the Lake Formation console or using service APIs. +Amazon S3 Tables integrates with AWS Glue Data Catalog (Data Catalog) and registers the catalog as a Lake Formation data location. You can set up this registration from the Lake Formation console or by using the service APIs. @@ -9 +9,5 @@ You can integrate Amazon S3 table buckets and tables with AWS Glue Data Catalog -The following limitations apply to integrating S3 tables catalog with Data Catalog and Lake Formation: +###### Note + +If you have an IAM or S3 Tables resource-based policy that restricts IAM users and IAM roles based on principal tags, you must attach the same principal tags to the IAM role that Lake Formation uses to access your S3 data (for example, LakeFormationDataAccessRole) and grant this role the necessary permissions. This is required for your tag-based access control policy to work correctly with your S3 Tables analytics integration. + +The following limitations apply to integrating S3 Tables catalog with Data Catalog and Lake Formation: @@ -15 +19 @@ The following limitations apply to integrating S3 tables catalog with Data Catal - * The SearchTables API cannot search S3 tables. + * The SearchTables API cannot search S3 Tables.