-
Amazon S3
- S3 Bucket Acl Operations
- S3 Bucket Cors Operations
- S3 Bucket Is Stale Allowed Operations
- S3 Bucket Lifecycle Operation
- S3 Bucket List Uploads Operations
- S3 Bucket Location Operations
- S3 Bucket Operations
- S3 Bucket Versioning Operations
- S3 Bucket Versions Operations
- S3 Data Node Operation
- S3 Multi Object Delete Operations
- S3 Object Acl Operations
- S3 Object Init Uploads Operations
- S3 Object Operations
- S3 Object Uploads Operations
- S3 Options Operations
- S3 Ping Operation
- EMC Atmos
- OpenStack SWIFT
- All Changes
-
Modified Services
- Data Store
- Password Group (Swift)
- S3 Bucket Acl Operations
- S3 Bucket Lifecycle Operation
- S3 Bucket Location Operations
- S3 Bucket Operations
- S3 Bucket Versioning Operations
- S3 Object Operations
- S3 Object Uploads Operations
- Secret Key
- Secret Key Self-Service
- Swift Container Operations
- Swift File Access Operations
- Swift Object Operations
- User (Object)
Changes to Create Bucket
Creates a new bucket.
Only authenticated users can create buckets, anonymous requests are never allowed to create buckets. The current user will become the bucket owner. Bucket region parameters will be ignored, and US Standard region will be always used.
The bucket ACL can be set with the bucket creation request, but it is optional. If the ACL is supplied, it can be specified with a canned ACL using the x-amz-acl request header, or specified explicitly using the x-amz-grant-read, x-amz-grant-write, x-amz-grant-read-acp, x-amz-grant-write-acp, x-amz-grant-full-control headers. These headers map to the set of permissions S3 supports in an ACL. If both are specified, the canned ACL will be ignored.
When using host style addressing, the url is of the form: bucketname.ns1.emc.com, where ns1 is the namespace, and emc.com is the base url.
Rules for Bucket NamingBucket names must comply with the following rules in order to be DNS compliant:
Bucket names must be at least 3 and no more than 63 characters long
Bucket name must be a series of one or more labels separated by a period (.)
Bucket names can contain lowercase letters, numbers and dashes
Bucket names must not be formatted as an IP address (for example 192.168.5.4).
Request Header Changes
| x-emc-namespace | optional | Namespace to be used for this bucket. If the namespace is not specified using the S3 convention of host/path style request, it can be specified using the x-emc-namespace header. If the namespace is not specified in this header either, and if the request is from a registered user, the namespace associated with that user is used. If all of these attempts fail, the request is rejected. |
| x-emc-vpool | optional | The replication group to associate the new bucket with. This determines the data stores used to store the objects associated with this bucket. If this header is not present, the default replication group defined for the associated namespace is used. |
| x-amz-acl | optional | The canned ACL to apply to the bucket you are creating. Valid Values: private, public-read, public-read-write, authenticated-read, bucket-owner-read, bucket-owner-full-control |
| x-amz-grant-read | optional | Allows grantee to list the objects in the bucket |
| x-amz-grant-write | optional | Allows grantee to create, overwrite and delete any object in the bucket |
| x-amz-grant-read-acp | optional | Enables the grantee(s) to read the ACL of the bucket. |
| x-amz-grant-write-acp | optional | Enables the grantee(s) to write or set the ACL for the bucket. |
| x-amz-grant-full-control | optional | Enables the grantee(s) read, write, READ_ACP and WRITE_ACP permissions on the bucket. |
| x-emc-retention-period | optional | Implicitly applying retention period in seconds for all objects in bucket, -1 denotes infinity |
| x-amz-date | optional | The current date and time according to the requester. Example: Wed, 01 Mar 2009 12:00:00 GMT. When you specify the Authorization header, you must specify either the x-amz-date or the Date header. If you specify both, the value specified for the x-amz-date header takes precedence. |
| x-emc-file-system-access-enabled | optional | Flag that indicates whether the bucket can be accessed as HDFS |
| x-emc-is-stale-allowed | optional | Container Flag that indicates whether the bucket can be accessed during a temporary VDC outage in a federated configuration |