How is S3 Express One Zone different? - Amazon Simple Storage Service
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

How is S3 Express One Zone different?

Amazon S3 Express One Zone is a high-performance, single-zone Amazon S3 storage class that is purpose-built to deliver consistent, single-digit millisecond data access for your most latency-sensitive applications. S3 Express One Zone is the first S3 storage class where you can select a single Availability Zone with the option to co-locate your object storage with your compute resources, which provides the highest possible access speed. Additionally, to further increase access speed and support hundreds of thousands of requests per second, S3 Express One Zone data is stored in a new bucket type: an Amazon S3 directory bucket.

For more information, see What is S3 Express One Zone? and Directory buckets.

You can create directory buckets and access your data in S3 Express One Zone by using the Amazon S3 API. The Amazon S3 API is compatible with S3 Express One Zone and directory buckets, with the exception of a few notable differences. For more information about how S3 Express One Zone is different, see the following topics.

S3 Express One Zone differences

  • Supported bucket type – Objects in the S3 Express One Zone storage class can only be stored in directory buckets. For more information, see Directory buckets.

  • Durability – With S3 Express One Zone, your data is redundantly stored on multiple devices within a single Availability Zone. S3 Express One Zone is designed for 99.95% availability within a single Availability Zone and is backed by the Amazon S3 Service Level Agreement. For more information, see Single Availability Zone.

  • ListObjectsV2 behavior – For directory buckets, ListObjectsV2 does not return objects in lexicographical (alphabetical) order. Additionally, prefixes must end in a delimiter and only "/" can be specified as the delimiter.

  • Deletion behavior – When you delete an object in a directory bucket, Amazon S3 recursively deletes any empty directories in the object path. For example, if you delete the object key dir1/dir2/file1.txt, Amazon S3 deletes file1.txt. If the dir1/ and dir2/ directories are empty and contain no other objects, Amazon S3 also deletes those directories.

  • ETags and checksums – Entity tags (ETags) for S3 Express One Zone are random alphanumeric strings and not MD5 checksums. For more information about using additional checksums with S3 Express One Zone, see S3 additional checksum best practices.

  • Object keys in DeleteObjects requests

    • Object keys in DeleteObjects requests must contain at least one non-white space character. Strings of all white space characters aren't supported in DeleteObjects requests.

    • Object keys in DeleteObjects requests cannot contain Unicode control characters, except for the newline (\n), tab (\t), and carriage return (\r) characters.

  • Regional and Zonal endpoints – When using S3 Express One Zone, you must specify the Region in all client requests. For Regional endpoints, you specify the Region, for example, s3express-control.us-west-2.amazonaws.com. For Zonal endpoints, you specify both the Region and the Availability Zone, for example, s3express-usw2-az1.us-west-2.amazonaws.com. For more information, see Regional and Zonal endpoints.

  • Multipart uploads – As with other objects stored in Amazon S3, you can upload and copy large objects that are stored in the S3 Express One Zone storage class by using the multipart upload process. However, the following are some differences when using the multipart upload process with objects stored in S3 Express One Zone. For more information, see Using multipart uploads with directory buckets.

    • The object creation date is the completion date of the multipart upload.

    • Multipart part numbers must use consecutive part numbers. If you try to complete a multipart upload request with nonconsecutive part numbers, Amazon S3 generates an HTTP 400 (Bad Request) error.

    • The initiator of a multipart upload can abort the multipart upload request only if they have been granted explicit allow access to AbortMultipartUpload through the s3express:CreateSession permission. For more information, see Amazon Identity and Access Management (IAM) for S3 Express One Zone.

API operations supported by S3 Express One Zone

The Amazon S3 Express One Zone storage class supports both Regional (bucket level, or control plane) and Zonal (object level, or data plane) endpoint API operations. For more information, see Networking for S3 Express One Zone and Endpoints and gateway VPC endpoints.

Regional endpoint API operations

The following Regional endpoint API operations are supported for S3 Express One Zone:

Zonal endpoint API operations

The following Zonal endpoint API operations are supported for S3 Express One Zone:

Amazon S3 features not supported by S3 Express One Zone

The following Amazon S3 features are not supported by S3 Express One Zone:

  • Amazon CloudTrail data plane events

  • Amazon managed policies

  • Amazon PrivateLink for S3

  • MD5 checksums

  • Multi-factor authentication (MFA) delete

  • S3 Object Lock

  • Requester Pays

  • S3 Access Grants

  • S3 Access Points

  • Bucket tags

  • Amazon CloudWatch request metrics

  • S3 Event Notifications

  • S3 Lifecycle

  • S3 Multi-Region Access Points

  • S3 Object Lambda Access Points

  • S3 Versioning

  • S3 Inventory

  • S3 Replication

  • Object tags

  • S3 Select

  • Server access logs

  • Static website hosting

  • S3 Storage Lens

  • S3 Storage Lens groups

  • S3 Transfer Acceleration

  • Dual-layer server-side encryption with Amazon Key Management Service (Amazon KMS) keys (DSSE-KMS)

  • Server-side encryption with Amazon Key Management Service (Amazon KMS) keys (SSE-KMS)

  • Server-side encryption with customer-provided keys (SSE-C)