| Table of Contents | ||
|---|---|---|
|
...
| Info |
|---|
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 Bucket Restrictions in Amazon S3.
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 of the 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.
...
| Info |
|---|
Delete BucketThe Settings > Delete Bucket command deletes not only the bucket but also and all of its 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. |
...
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 Bucket Restrictions in Amazon S3.
| Info |
|---|
TipBy following S3 compatibility restrictions in naming, general compatibility of bucket names is improved with any future application integrations needed. |
...