AWS AmazonS3 documentation change
Summary
Updated documentation to consistently specify 'for general purpose buckets' in access point naming rules and limitations sections
Security assessment
Changes focus on clarifying scope to general purpose buckets without introducing new security content or addressing vulnerabilities. Mentions of access control (e.g., cross-account permissions) remain unchanged except for scope clarification.
Diff
diff --git a/AmazonS3/latest/userguide/access-points-restrictions-limitations-naming-rules.md b/AmazonS3/latest/userguide/access-points-restrictions-limitations-naming-rules.md index 34f8e35fc..70cd57643 100644 --- a/AmazonS3/latest/userguide/access-points-restrictions-limitations-naming-rules.md +++ b/AmazonS3/latest/userguide/access-points-restrictions-limitations-naming-rules.md @@ -5 +5 @@ -Naming rules for Amazon S3 access pointsRestrictions and limitations for access points +Naming rules for Amazon S3 access points for general purpose bucketsRestrictions and limitations for access points for general purpose buckets @@ -7 +7 @@ Naming rules for Amazon S3 access pointsRestrictions and limitations for access -# Access points naming rules, restrictions, and limitations +# Access points for general purpose buckets naming rules, restrictions, and limitations @@ -9 +9 @@ Naming rules for Amazon S3 access pointsRestrictions and limitations for access -Access points are named network endpoints attached to a bucket to simplify managing data. When you create an access point you choose a name and the AWS Region to create it in. The following topics provide information about access point naming rules and restrictions and limitations. +Access points for general purpose buckets are named network endpoints attached to a bucket to simplify managing data. When you create an access point you choose a name and the AWS Region to create it in. The following topics provide information about access point naming rules and restrictions and limitations. @@ -13 +13 @@ Access points are named network endpoints attached to a bucket to simplify manag - * Naming rules for Amazon S3 access points + * Naming rules for Amazon S3 access points for general purpose buckets @@ -15 +15 @@ Access points are named network endpoints attached to a bucket to simplify manag - * Restrictions and limitations for access points + * Restrictions and limitations for access points for general purpose buckets @@ -20 +20 @@ Access points are named network endpoints attached to a bucket to simplify manag -## Naming rules for Amazon S3 access points +## Naming rules for Amazon S3 access points for general purpose buckets @@ -22 +22 @@ Access points are named network endpoints attached to a bucket to simplify manag -When you create an access point you choose its name and the AWS Region to create it in. Unlike general purpose buckets access point names do not need to be unique across AWS accounts or AWS Regions. The same AWS account may create access points with the same name in different AWS Regions or two different AWS accounts may use the same access point name. However, within a single AWS Region an AWS account may not have two identically named access points. +When you create an access point for a general purpose bucket, you choose its name and the AWS Region to create it in. Unlike general purpose buckets access point names do not need to be unique across AWS accounts or AWS Regions. The same AWS account may create access points with the same name in different AWS Regions or two different AWS accounts may use the same access point name. However, within a single AWS Region an AWS account may not have two identically named access points. @@ -40 +40 @@ Access point names must be DNS-compliant and must meet the following conditions: - * Can't end with the suffix `-s3alias`. This suffix is reserved for access point alias names. For more information, see [Access point aliases](./access-points-naming.html#access-points-alias). + * Can't end with the suffix `-s3alias`. This suffix is reserved for access point alias names. For more information, see [Access point for general purpose buckets aliases](./access-points-naming.html#access-points-alias). @@ -45 +45 @@ Access point names must be DNS-compliant and must meet the following conditions: -## Restrictions and limitations for access points +## Restrictions and limitations for access points for general purpose buckets @@ -47 +47 @@ Access point names must be DNS-compliant and must meet the following conditions: -Amazon S3 access points have the following restrictions and limitations: +Amazon S3 access points for general purpose buckets have the following restrictions and limitations: @@ -49 +49 @@ Amazon S3 access points have the following restrictions and limitations: - * Each access point is associated with exactly one bucket, which you must specify when you create the access point. After you create an access point, you can't associate it with a different bucket. However, you can delete an access point, and then create another one with the same name and associate that new access point with a different bucket. + * Each access point for general purpose buckets is associated with exactly one general purpose bucket, which you must specify when you create the access point. After you create an access point, you can't associate it with a different bucket. However, you can delete an access point, and then create another one with the same name and associate that new access point with a different bucket. @@ -71 +71 @@ Amazon S3 access points have the following restrictions and limitations: - * Cross-account access points don’t grant you access to data until you are granted permissions from the bucket owner. The bucket owner always retains ultimate control over access to the data and must update the bucket policy to authorize requests from the cross-account access point. To view a bucket policy example, see [Configuring IAM policies for using access points](./access-points-policies.html). + * Cross-account access points don’t grant you access to data until you are granted permissions from the bucket owner. The bucket owner always retains ultimate control over access to the data and must update the bucket policy to authorize requests from the cross-account access point. To view a bucket policy example, see [Configuring IAM policies for using access points for general purpose buckets](./access-points-policies.html). @@ -86 +86 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Working with access points +Working with access points for general purpose buckets