BangmodStorage

Bucket lifecycle

Naming rules

Bucket names must be valid S3-compatible and uniquely addressable across our entire service. The constraints below match AWS S3 except where noted:

  • 3 to 63 characters long
  • Lowercase letters, digits, hyphens. No whitespace, no underscores, no uppercase.
  • Must start and end with a letter or digit
  • Cannot be formatted as an IP address (e.g. 192.168.1.1)
  • Cannot start with xn-- (reserved for IDN)
  • Cannot start with bgs- (reserved for internal buckets)
  • Globally unique across all BangmodStorage customers

When you attempt to create a bucket with whitespace or other invalid characters, we return InvalidBucketName with a message explaining the violation.

Creating a bucket

Use any S3 SDK or the customer console at /console/buckets. New buckets are created in the region of the access key used; specify the region at sign-up or by issuing a region-matched key.

Versioning

Versioning is per-bucket. Enable via PutBucketVersioning or from the bucket settings tab. Versioning has compute and storage cost implications: each PUT to a versioned bucket creates a new version that is billed for storage until you delete it.

Lifecycle rules

Set object expiration, multi-part-upload cleanup, and (when storage classes ship) transition rules via PutBucketLifecycleConfiguration. Lifecycle rules evaluated daily; expired objects deleted within 24 hours of the rule firing.

Recommend always setting an "Abort incomplete multipart upload after 7 days" rule to avoid paying for orphaned parts.

Deletion

Deleting a bucket requires it to be empty. To delete a non-empty bucket, first empty its contents via aws s3 rm s3://bucket/ --recursive or equivalent. We require explicit confirmation in the console for the same operation.

Bucket names freed by deletion are not reusable for 14 days, to prevent accidental access to old data via name re-registration.

Public access

Buckets default to private. To make a bucket public, set a canned ACL of public-read or apply a bucket policy granting anonymous read. We recommend bucket policies over ACLs for finer-grained control. Public buckets count toward different egress accounting (see Limits).