Skip to content
Stackship documentation Svenska

S3 storageUsers

Names and limits

Naming rules for storage accounts and buckets, how the quota is enforced, and which S3 operations are supported.

Storage account names

  • 3 to 50 characters in the portal: lowercase letters, digits and hyphens, starting with a letter and ending with a letter or digit.
  • Unique across the whole platform, because the name is part of the default endpoint <account>.s3.example.com.
  • Fixed after creation.

Bucket names

  • 3 to 63 characters: lowercase letters, digits and hyphens, starting and ending with a letter or digit.
  • No dots, and nothing shaped like an IPv4 address.
  • Unique within the storage account. Two accounts can each have a bucket with the same name.

Quota

  • The quota is the size of the account's volume. It is set when the account is created and cannot be changed in the portal; the volume never grows.
  • The server measures what is stored every five minutes. An upload (PutObject or UploadPart) is refused with 507 InsufficientStorage when the last measurement plus the upload's size would go past 99 % of the quota.
  • Because the measurement can be up to five minutes old, uploads in between can go further. When the volume itself is full, writes fail with 507 InsufficientStorage too.
  • Deleting objects frees room from the next measurement on.

Server

  • Each account has one S3 server. While it restarts — after a configuration change, for example — the endpoint is briefly unavailable.
  • Changes to access keys and buckets reach the server within about five seconds.

Supported operations

Area Operations
Buckets ListBuckets, HeadBucket, CreateBucket, DeleteBucket
Objects ListObjectsV2, GetObject (including byte ranges), HeadObject, PutObject, CopyObject, DeleteObject, DeleteObjects
Multipart uploads CreateMultipartUpload, UploadPart, CompleteMultipartUpload, AbortMultipartUpload, ListParts

CopyObject copies within the same storage account. Operations not listed are not supported: there is no versioning, no object lock, no bucket policy or ACL, no lifecycle rules, no CORS configuration per bucket and no virtual-hosted-style addressing.