Object Storage buckets

Quake AI concept: Containers

• Linode exposes buckets through a dedicated Object Storage API rather than as Swift containers. The canonical API summary lists `GET /{apiVersion}/object-storage/buckets` to list buckets, `POST /{apiVersion}/object-storage/buckets` to create one, and region-scoped bucket routes such as `/{apiVersion}/object-storage/buckets/{regionId}/{bucket}` for get and delete operations (Linode API summary).
• Buckets are region-scoped in the API, with a separate `regionId` path segment and a separate `GET /object-storage/buckets/{regionId}` operation for listing buckets in a region. That is different from OpenStack Swift's account/container model, where containers are not modeled as a region-scoped resource in the same way (Linode API summary).
• The service is explicitly S3-compatible rather than Swift-native. Linode documents use of `aws s3` and `aws s3api`, require an explicit endpoint URL such as `https://us-southeast-1.linodeobjects.com`, and note that `Akamai Object Storage does not support the get-object-attributes command` (Use the AWS CLI with Object Storage).
• Linode publishes bucket-level quotas and rate limits, including a default `1,000` buckets per account per endpoint and per-bucket RPS caps that vary by endpoint type; rate-limited requests receive `503` responses and users are told to spread data across multiple buckets to avoid limits (Object Storage quotas and limits).