Creating a directory bucket
To start using the Amazon S3 Express One Zone storage class, you create a directory bucket. The
S3 Express One Zone storage class can be used only with directory buckets. The S3 Express One Zone storage class supports
low-latency use cases and provides faster data processing within a single Availability Zone. If
your application is performance sensitive and benefits from single-digit millisecond
PUT
and GET
latencies, we recommend creating a directory bucket so
that you can use the S3 Express One Zone storage class.
There are two types of Amazon S3 buckets, general purpose buckets and directory buckets. You should choose the bucket type that best fits your application and performance requirements. General purpose buckets are the original S3 bucket type. General purpose buckets are recommended for most use cases and access patterns and allow objects stored across all storage classes, except S3 Express One Zone. For more information about general purpose buckets, see Buckets overview.
Directory buckets use the S3 Express One Zone storage class, which is designed to be used for workloads or performance-critical applications that require consistent single-digit millisecond latency. 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. When you create a directory bucket, you can optionally specify an AWS Region and an Availability Zone that's local to your Amazon EC2, Amazon Elastic Kubernetes Service, or Amazon Elastic Container Service (Amazon ECS) compute instances to optimize performance.
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 percent availability within a single Availability Zone and is backed
by the Amazon S3 Service Level Agreement
Directory buckets organize data hierarchically into directories, as opposed to the flat storage structure of general purpose buckets. There aren't prefix limits for directory buckets, and individual directories can scale horizontally.
For more information about directory buckets, see Directory buckets overview.
Directory bucket names
Directory bucket names must follow this format and comply with the rules for directory bucket naming:
bucket-base-name
--azid
--x-s3
For example, the following directory bucket name contains the Availability Zone ID usw2-az1
:
bucket-base-name
--usw2-az1--x-s3
For more information about directory bucket naming rules, see Directory bucket naming rules.
Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/
. -
In the navigation bar on the top of the page, choose the name of the currently displayed AWS Region. Next, choose the Region in which you want to create a bucket.
Note
To minimize latency and costs and address regulatory requirements, choose a Region close to you. Objects stored in a Region never leave that Region unless you explicitly transfer them to another Region. For a list of Amazon S3 AWS Regions, see AWS service endpoints in the Amazon Web Services General Reference.
-
In the left navigation pane, choose Buckets.
-
Choose Create bucket.
The Create bucket page opens.
-
Under General configuration, view the AWS Region where your bucket will be created.
-
Under Bucket type, choose Directory.
Note
-
If you've chosen a Region that doesn't support directory buckets, the Bucket type option disappears, and the bucket type defaults to a general purpose bucket. To create a directory bucket, you must choose a supported Region. For a list of Regions that support directory buckets and the Amazon S3 Express One Zone storage class, see S3 Express One Zone Availability Zones and Regions.
-
After you create the bucket, you can't change the bucket type.
For Availability Zone, choose a Availability Zone local to your compute services. For a list of Availability Zones that support directory buckets and the S3 Express One Zone storage class, see S3 Express One Zone Availability Zones and Regions.
Note
The Availability Zone can't be changed after the bucket is created.
-
-
Under Availability Zone, select the check box to acknowledge that in the event of an Availability Zone outage, your data might be unavailable or lost.
Important
Although directory buckets are stored across multiple devices within a single Availability Zone, directory buckets don't store data redundantly across Availability Zones.
-
For Bucket name, enter a name for your directory bucket.
The following naming rules apply for directory buckets.
-
Be unique within the chosen AWS Region and Availability Zone.
-
Name must be between 3 (min) and 63 (max) characters long, including the suffix.
-
Consists only of lowercase letters, numbers and hyphens (-).
-
Begin and end with a letter or number.
-
Must include the following suffix:
--
.azid
--x-s3 -
Bucket names must not start with the prefix
xn--
. -
Bucket names must not start with the prefix
sthree-
. -
Bucket names must not start with the prefix
sthree-configurator
. -
Bucket names must not start with the prefix
amzn-s3-demo-
. -
Bucket names must not end with the suffix
-s3alias
. This suffix is reserved for access point alias names. For more information, see Using a bucket-style alias for your S3 bucket access point. -
Bucket names must not end with the suffix
--ol-s3
. This suffix is reserved for Object Lambda Access Point alias names. For more information, see How to use a bucket-style alias for your S3 bucket Object Lambda Access Point. -
Bucket names must not end with the suffix
.mrap
. This suffix is reserved for Multi-Region Access Point names. For more information, see Rules for naming Amazon S3 Multi-Region Access Points.
A suffix is automatically added to the base name that you provide when you create a directory bucket using the console. This suffix includes the Availability Zone ID of the Availability Zone that you chose.
After you create the bucket, you can't change its name. For more information about naming buckets, see Bucket naming rules.
Important
Do not include sensitive information, such as account numbers, in the bucket name. The bucket name is visible in the URLs that point to the objects in the bucket.
-
-
Under Object Ownership, the Bucket owner enforced setting is automatically enabled, and all access control lists (ACLs) are disabled. For directory buckets, ACLs can't be enabled.
ACLs disabled
-
Bucket owner enforced (default) – ACLs are disabled, and the bucket owner automatically owns and has full control over every object in the bucket. ACLs no longer affect access permissions to data in the S3 bucket. The bucket uses policies exclusively to define access control.
A majority of modern use cases in Amazon S3 no longer require the use of ACLs. For more information, see Controlling ownership of objects and disabling ACLs for your bucket.
-
-
Under Block Public Access settings for this bucket, all Block Public Access settings for your directory bucket are automatically enabled. These settings can't be modified for directory buckets. For more information about blocking public access, see Blocking public access to your Amazon S3 storage.
-
Under Server-side encryption settings, directory buckets use Server-side encryption with Amazon S3 managed keys (SSE-S3) to encrypt data.
-
Choose Create bucket.
After creating the bucket, you can add files and folders to the bucket. For more information, see Working with objects in a directory bucket.
This example shows how to create a directory bucket by using the AWS CLI. To use the command replace the user input placeholders
with your own information.
When you create a directory bucket you must provide configuration details and use the following naming convention:
bucket-base-name
--azid
--x-s3
aws s3api create-bucket --bucket
bucket-base-name
--azid
--x-s3 --create-bucket-configuration 'Location={Type=AvailabilityZone,Name=usw2-az1
},Bucket={DataRedundancy=SingleAvailabilityZone,Type=Directory}' --regionus-west-2
For more information, see create-bucket