AWS AmazonS3 documentation change
Summary
Updated bucket naming requirements, added opt-in status details to API documentation, and removed explanations about network architecture/endpoint routing
Security assessment
Changes focus on technical accuracy and documentation structure rather than security features. Removed network architecture details describe infrastructure design but do not directly impact security controls or vulnerabilities.
Diff
diff --git a/AmazonS3/latest/userguide/s3-lzs-for-directory-buckets.md b/AmazonS3/latest/userguide/s3-lzs-for-directory-buckets.md index 383e73007..fb9cf0cd9 100644 --- a//AmazonS3/latest/userguide/s3-lzs-for-directory-buckets.md +++ b//AmazonS3/latest/userguide/s3-lzs-for-directory-buckets.md @@ -7 +7 @@ -Before creating a directory bucket in an AWS Local Zone (Local Zone), it's essential to know the Local Zone ID where you want to create a bucket. You can obtain a list of Local Zone IDs by using the [DescribeAvailabilityZones](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeAvailabilityZones.html) API operation. This API operation provides information about Local Zones (including Local Zone IDs), their parent Regions, and network border groups. The directory bucket name consists of a base name that you provide and a suffix that contains the Zone ID of your bucket location. +Before creating a directory bucket in a Local Zone, you must have the Local Zone ID where you want to create a bucket. You can find all Local Zone information by using the [DescribeAvailabilityZones](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeAvailabilityZones.html) API operation. This API operation lists information about Local Zones, including their Local Zone IDs, parent Region names, network border groups, and opt-in status. After you have your Local Zone ID, you can create a directory bucket in the Local Zone. The directory bucket name consists of a base name that you provide and a suffix that contains the Zone ID of your bucket location, followed by `--x-s3`. @@ -9,5 +9 @@ Before creating a directory bucket in an AWS Local Zone (Local Zone), it's essen -A Local Zone is connected to the **parent Region** using the Amazon redundant and very high-bandwidth private network. This gives applications running in the Local Zone fast, secure, and seamless access to the rest of the AWS services. **Parent Zone ID** is the ID of the zone that handles some of the Local Zone control plane operations, such as API calls. **Network Border Group** is a unique group from which AWS advertises public IP addresses. For more information about Local Zones, parent Region, and parent Zone ID, see [AWS Local Zones concepts](https://docs.aws.amazon.com/local-zones/latest/ug/concepts-local-zones.html) in the AWS Local Zones _User Guide_. - -All directory buckets use the `s3express` namespace, which is different from the `s3` namespace for general purpose buckets. For directory buckets, requests are routed to either a **Regional endpoint** or a **Zonal endpoint**. The routing is handled automatically for you if you use the AWS Management Console, AWS CLI, or AWS SDKs. - -Bucket-level API operations (such as `CreateBucket` and `DeleteBucket`) are routed to Regional endpoints, and are referred to as Regional endpoint API operations. Regional endpoints are in the format of `s3express-control.ParentZoneID.amazonaws.com`. All object-level API operations (such as `PutObject`) and two bucket-level API operations (`CreateSession` and `HeadBucket`) are routed to Zonal endpoints, and are referred to as Zonal endpoint API operations. Zonal endpoints are in the format of `s3express-LocalZoneID.ParentRegionCode.amazonaws.com`. For a complete list of API operations by endpoint type, see [Directory bucket API operations](https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-differences.html#s3-express-differences-api-operations). +All directory buckets use the `s3express` namespace, which is separate from the `s3` namespace for general purpose buckets. For directory buckets, requests are routed to either a **Regional endpoint** or a **Zonal endpoint**. The routing is handled automatically for you if you use the AWS Management Console, AWS CLI, or AWS SDKs. @@ -25 +21 @@ Data residency workloads -Enable accounts for Dedicated Local Zones +Enable accounts for Local Zones