The StorageGRID Webscale system supports a maximum of 1,000 buckets for each S3 tenant account.
Bucket name restrictions follow the AWS US Standard region restrictions, but you should further restrict them to DNS naming conventions in order to support S3 virtual hosted-style requests.
The GET Bucket (List Objects) and GET Bucket versions operations support StorageGRID Webscale consistency controls.
You can check whether updates to last access time are enabled or disabled for individual buckets.
The following table describes how StorageGRID Webscale implements S3 REST API bucket operations. To perform any of these operations, the necessary access credentials must be provided for the account.
Operation | Implementation |
---|---|
DELETE Bucket | Implemented with all Amazon S3 REST API behavior. |
DELETE Bucket cors | This operation deletes the CORS configuration for the bucket. |
DELETE Bucket policy | This operation deletes the policy attached to the bucket. |
DELETE Bucket replication | This operation deletes the replication configuration attached to the bucket. |
GET Bucket (List Objects), version 1 | This operation returns some or all (up to 1,000) of the objects in a bucket. The Storage Class for objects is always listed as STANDARD, even if the object was ingested with the REDUCED_REDUNDANCY storage class option. Requests that traverse a large number of keys require special handling. The request might return a truncated response or an empty response to avoid timing out. To get the complete set of results, you need to continue making requests while updating the marker parameter, as you normally do with a truncated result. Always use NextMarker if it is present. In some cases, the StorageGRID Webscale implementation of the S3 REST API returns a NextMarker, when the Amazon S3 REST API would not, because it is a better marker than the last key returned. |
GET Bucket acl | This operation returns a positive response and the ID, DisplayName, and Permission of the bucket owner, indicating that the owner has full access to the bucket. |
GET Bucket cors | This operation returns the cors configuration for the bucket. |
GET Bucket location | This operation returns the bucket's region. By default, us-east-1 is returned unless a region was set using the LocationConstraint element in the PUT Bucket request. |
GET Bucket Object versions | With READ access on a bucket, this operation with the versions subresource lists metadata of all of the versions of objects in the bucket. |
GET Bucket notification | This operation returns the notification configuration attached to the bucket. |
GET Bucket policy | This operation returns the policy attached to the bucket. |
GET Bucket replication | This operation returns the replication configuration attached to the bucket. |
GET Bucket versioning | This implementation uses the versioning subresource to return the versioning state of a bucket. The versioning state returned indicates if the bucket is "Unversioned" or if the bucket is version "Enabled" or "Suspended." |
HEAD Bucket | This operation determines if a bucket exists and you have permission to access it. |
PUT Bucket | This operation creates a new bucket. By creating the bucket, you become the bucket owner.
|
PUT Bucket cors | This operation sets the CORS configuration for a bucket so that the bucket can service cross-origin requests. Cross-origin resource sharing (CORS) is a security mechanism that allows client web applications in one domain to access resources in a different domain. For example, suppose you use an S3 bucket named images to store graphics. By setting the CORS configuration for the images bucket, you can allow the images in that bucket to be displayed on the website http://www.example.com. |
PUT Bucket notification | This operation configures notifications for the bucket using the notification configuration XML included in the request body. You should be aware of the following implementation details:
|
PUT Bucket policy | This operation sets the policy attached to the bucket. |
PUT Bucket replication | This operation configures StorageGRID Webscale CloudMirror replication for the bucket using the replication configuration XML provided in the request body. For CloudMirror replication, you should be aware of the following implementation details:
|
PUT Bucket versioning | This implementation uses the versioning subresource to set the versioning state of an existing bucket. You can set the versioning state with one of the following values:
|