Within a domain, a bucket is the primary entity for managing uploaded content. Buckets have these essential features:
Ownership: Each bucket has an owner.
Access control: Buckets can define separate permissions so users and groups within them are separated from those in other buckets.
Content: The bucket itself stores end-user data as named objects.
Unnamed ObjectsUnnamed objects cannot be written to buckets, but they can be written directly to the domain itself. Unnamed objects are contained in the system-controlled, read-only Content IDs bucket part of each domain. |
See the Naming Rules for Swarm for buckets and http://docs.aws.amazon.com/AmazonS3/latest/dev/BucketRestrictions.html.
Bucket Usage: The Storage column displays the current size of the storage footprint used by all buckets, inclusive of all versions, replicas, and erasure-coded segments when viewing all buckets in a given domain. The Bandwidth column displays the total bandwidth (both bytes in and bytes out) used by all buckets over a rolling 30 day window. See Usage Reports.
A bucket reports its own usage at the top of the page, along with its total object count:
Dynamic Filtering: Narrow the listing by entering a string in the Filter box, which filters by Name if a large number of buckets and/or collections exist.
File Uploading: Use the Uploads icon to the far right of the listed buckets to initiate uploads from the local file system.
Delete BucketThe Settings > Delete Bucket command deletes the bucket and all uploaded contents. This command cannot be undone, so proceed with caution. Deleted objects may continue to appear in Collection listings for a period of time after they are deleted, but they are no longer accessible in the cluster. |
Provide a name to add a bucket. The Add button becomes active for selection when the name is validated:
S3 compatible: The bucket name needs to use lowercase alphanumeric characters and stay within 3 to 63 characters in length. The name is validated with dynamic feedback while typing:
See http://docs.aws.amazon.com/AmazonS3/latest/dev/BucketRestrictions.html.
TipBy following S3 compatibility restrictions in naming, general compatibility of bucket names is improved with any future application integrations needed. |
Every bucket must have an owner, who has access to and authority over its entirety.
Ownership defaults to the person who created the bucket, but the owner does not need to be a domain administrator.
Ownership defaults to the person who created the bucket, but the owner does not need to be a domain administrator.
Change the owner when creating a context for someone else to manage. Do not own or be responsible for managing the data in the bucket if creating a bucket for a client to use with an application.
Storage policies control how this bucket's objects are protected (via replication and/or erasure coding) and whether they are versioned. By default, the bucket inherits the storage policies in force for the cluster and the domain.
Specify custom policies, but these custom policies are subject to what is allowed and in force in the cluster and the domain if inheriting these policies is disabled. A warning icon and message alerts to the situation if opting for something being overridden by a higher policy.
Permissions are determined by the access control policy, which are the rules granting (or denying) users and groups the ability to perform specific actions.
See Setting Permissions and Gateway Access Control Policies.