AWS prescriptive-guidance documentation change
Summary
Updated image path and reformatted ACL note with horizontal rule
Security assessment
The image path change is purely cosmetic. The ACL note clarification documents existing behavior but doesn't address a vulnerability or introduce new security features.
Diff
diff --git a/prescriptive-guidance/latest/migration-large-mysql-mariadb-databases/amazon-s3-file-gateway.md b/prescriptive-guidance/latest/migration-large-mysql-mariadb-databases/amazon-s3-file-gateway.md index 1cbfc3466..8614ae5be 100644 --- a//prescriptive-guidance/latest/migration-large-mysql-mariadb-databases/amazon-s3-file-gateway.md +++ b//prescriptive-guidance/latest/migration-large-mysql-mariadb-databases/amazon-s3-file-gateway.md @@ -15 +15 @@ The following diagram shows the high-level steps involved when using Amazon S3 F - + @@ -61,3 +61,2 @@ The following are limitations when using Amazon S3 File Gateway file shares: -###### Note - -If you configure the ACLs on the root instead of the parent folder under the root, the ACL permissions aren't persistent in Amazon S3. +Note: If you configure the ACLs on the root instead of the parent folder under the root, the ACL permissions aren't persistent in Amazon S3. +---