The StorageGRID 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.
Amazon Web Services (AWS) Documentation: Bucket Restrictions and Limitations
Supporting S3 virtual-hosted style requests
The GET Bucket (List Objects) and GET Bucket versions operations support StorageGRID consistency controls.
You can check whether updates to last access time are enabled or disabled for individual buckets.
The following table describes how StorageGRID 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 lifecycle | This operation deletes the lifecycle configuration from 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. | ||||||||||
DELETE Bucket tagging | This operation uses the tagging subresource to remove all tags from a bucket. | ||||||||||
GET Bucket (List Objects), version 1 and version 2 | This operation returns some or all (up to 1,000) of the objects in a bucket. The Storage Class for objects can have either of two values, even if the object was ingested with the REDUCED_REDUNDANCY storage class option:
If the bucket contains large numbers of deleted keys that have the same prefix, the response might include some CommonPrefixes that do not contain keys. |
||||||||||
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 lifecycle | This operation returns the lifecycle configuration for the bucket. | ||||||||||
GET Bucket location | This operation returns the region that was set using the LocationConstraint element in the PUT Bucket request. If the bucket's region is us-east-1, an empty string is returned for the region. | ||||||||||
GET Bucket notification | This operation returns the notification configuration attached to the bucket. | ||||||||||
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 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 tagging | This operation uses the tagging subresource to return all tags for a 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 Unversionedor if the bucket is version Enabledor 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 lifecycle | This operation creates a new lifecycle configuration for the bucket or replaces an existing lifecycle configuration. StorageGRID supports up to 1,000 lifecycle rules in a lifecycle configuration. Each rule can include the following XML elements:
StorageGRID does not support these actions:
To understand how the Expiration action in a bucket lifecycle interacts with ILM placement instructions, see Note: Lifecycle configuration is not supported for compliant buckets.
|
||||||||||
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 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 tagging | This operation uses the tagging subresource to add or update a set of tags for a bucket. When adding bucket tags, be aware of the following limitations:
|
||||||||||
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:
|