Creates a new bucket. To create a bucket, you must register with Amazon S3 and have a valid AWS Access Key ID to authenticate requests. Anonymous requests are never allowed to create buckets. By creating the bucket, you become the bucket owner.
s3_create_bucket(ACL, Bucket, CreateBucketConfiguration,
GrantFullControl, GrantRead, GrantReadACP, GrantWrite, GrantWriteACP,
ObjectLockEnabledForBucket)
The canned ACL to apply to the bucket.
[required] The name of the bucket to create.
The configuration information for the bucket.
Allows grantee the read, write, read ACP, and write ACP permissions on the bucket.
Allows grantee to list the objects in the bucket.
Allows grantee to read the bucket ACL.
Allows grantee to create, overwrite, and delete any object in the bucket.
Allows grantee to write the ACL for the applicable bucket.
Specifies whether you want S3 Object Lock to be enabled for the new bucket.
svc$create_bucket( ACL = "private"|"public-read"|"public-read-write"|"authenticated-read", Bucket = "string", CreateBucketConfiguration = list( LocationConstraint = "EU"|"eu-west-1"|"us-west-1"|"us-west-2"|"ap-south-1"|"ap-southeast-1"|"ap-southeast-2"|"ap-northeast-1"|"sa-east-1"|"cn-north-1"|"eu-central-1" ), GrantFullControl = "string", GrantRead = "string", GrantReadACP = "string", GrantWrite = "string", GrantWriteACP = "string", ObjectLockEnabledForBucket = TRUE|FALSE )
Not every string is an acceptable bucket name. For information on bucket naming restrictions, see Working with Amazon S3 Buckets.
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 How to Select a Region for Your Buckets.
If you send your create bucket request to the s3.amazonaws.com
endpoint, 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.
When creating a bucket using this operation, you can optionally specify the accounts or groups that should be granted specific permissions on the bucket. 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 ACL.
Specify access permissions explicitly using the x-amz-grant-read
,
x-amz-grant-write
, x-amz-grant-read-acp
,
x-amz-grant-write-acp
, and x-amz-grant-full-control
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
AWS account
uri
-- if you are granting permissions to a predefined group
emailAddress
-- if the value specified is the email address of
an AWS account
Using email addresses to specify a grantee is only supported in the following AWS Regions:
US East (N. Virginia)
US West (N. California)
US West (Oregon)
Asia Pacific (Singapore)
Asia Pacific (Sydney)
Asia Pacific (Tokyo)
Europe (Ireland)
South America (S<U+00C3><U+00A3>o Paulo)
For a list of all the Amazon S3 supported Regions and endpoints, see Regions and Endpoints in the AWS General Reference.
For example, the following x-amz-grant-read
header grants the AWS
accounts identified by account IDs permissions to read object data
and its metadata:
x-amz-grant-read: id="11112222333", id="444455556666"
You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
The following operations are related to CreateBucket
:
PutObject
DeleteBucket
# NOT RUN {
# The following example creates a bucket.
svc$create_bucket(
Bucket = "examplebucket"
)
# The following example creates a bucket. The request specifies an AWS
# region where to create the bucket.
svc$create_bucket(
Bucket = "examplebucket",
CreateBucketConfiguration = list(
LocationConstraint = "eu-west-1"
)
)
# }
# NOT RUN {
# }
Run the code above in your browser using DataLab