AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
Creates a new S3 bucket. To create a bucket, you must register with Amazon S3 and have a valid Amazon Web Services Access Key ID to authenticate requests. Anonymous requests are never allowed to create buckets. By creating the bucket, you become the bucket owner.
Not every string is an acceptable bucket name. For information about bucket naming restrictions, see Bucket naming rules.
If you want to create an Amazon S3 on Outposts bucket, see Create Bucket.
By default, the bucket is created in the US East (N. Virginia) Region. You can optionally specify a Region in the request body. You might choose a Region to optimize latency, minimize costs, or address regulatory requirements. For example, if you reside in Europe, you will probably find it advantageous to create buckets in the Europe (Ireland) Region. For more information, see Accessing a bucket.
If you send your create bucket request to the
the request goes to the us-east-1 Region. Accordingly, the signature calculations
in Signature Version 4 must use us-east-1 as the Region, even if the location constraint
in the request specifies another Region where the bucket is to be created. If you
create a bucket in a Region other than US East (N. Virginia), your application must
be able to handle 307 redirect. For more information, see Virtual
hosting of buckets.
Access control lists (ACLs)
When creating a bucket using this operation, you can optionally configure the bucket ACL to specify the accounts or groups that should be granted specific permissions on the bucket.
If your CreateBucket request sets bucket owner enforced for S3 Object Ownership and
specifies a bucket ACL that provides access to an external Amazon Web Services account,
your request fails with a
400 error and returns the
error code. For more information, see Controlling
object ownership in the Amazon S3 User Guide.
There are two ways to grant the appropriate permissions using the request headers.
Specify a canned ACL using the
x-amz-acl request header. Amazon S3 supports
a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined
set of grantees and permissions. For more information, see Canned
Specify access permissions explicitly using the
headers. These headers map to the set of permissions Amazon S3 supports in an ACL.
For more information, see Access
control list (ACL) overview.
You specify each grantee as a type=value pair, where the type is one of the following:
id – if the value specified is the canonical user ID of an Amazon Web
uri – if you are granting permissions to a predefined group
emailAddress – if the value specified is the email address of an Amazon
Web Services account
Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:
US East (N. Virginia)
US West (N. California)
US West (Oregon)
Asia Pacific (Singapore)
Asia Pacific (Sydney)
Asia Pacific (Tokyo)
South America (São Paulo)
For a list of all the Amazon S3 supported Regions and endpoints, see Regions and Endpoints in the Amazon Web Services General Reference.
For example, the following
x-amz-grant-read header grants the Amazon
Web Services accounts identified by account IDs permissions to read object data and
x-amz-grant-read: id="11112222333", id="444455556666"
You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
In addition to
s3:CreateBucket, the following permissions are required
when your CreateBucket includes specific headers:
ACLs - If your
CreateBucket request specifies ACL permissions
and the ACL is public-read, public-read-write, authenticated-read, or if you specify
access permissions explicitly through any other ACL, both
s3:PutBucketAcl permissions are needed. If the ACL the
request is private or doesn't specify any ACLs, only
permission is needed.
Object Lock - If
ObjectLockEnabledForBucket is set to true in
s3:PutBucketVersioning permissions are required.
S3 Object Ownership - If your CreateBucket request includes the the
s3:PutBucketOwnershipControls permission is required.
The following operations are related to
This is an asynchronous operation using the standard naming convention for .NET 4.5 or higher. For .NET 3.5 the operation is implemented as a pair of methods using the standard naming convention of BeginPutBucket and EndPutBucket.
public virtual Task<PutBucketResponse> PutBucketAsync( String bucketName, CancellationToken cancellationToken )
The name of the bucket to create.
A cancellation token that can be used by other objects or threads to receive notice of cancellation.
.NET Core App:
Supported in: 3.1
Supported in: 2.0
Supported in: 4.5