DigitalOcean Spaces vs Wasabi Hot Cloud Storage

DigitalOcean Spaces

Per-bucket access keys with read or read-write-delete grants, an 800 operations a second limit per bucket and a 99.9 per cent SLA are all published. The MCP server manages keys and CDN endpoints only, not objects, and the S3 reference documents no error codes. A payment method is required before any bucket is created.

Wasabi Hot Cloud Storage

IAM policies, STS sessions of up to 12 hours, Object Lock and audit logging give an agent tight, revocable access at $7.99 a TB-month with no egress or request fees. No request limits are published with numbers for the S3 API, there is no OpenAPI file, and billing assumes 1 TB and 90 days of storage as minimums.

DigitalOcean Spaces

1. Set the endpoint to https://<region>.digitaloceanspaces.com and, in AWS SDKs other than Python's, set region to us-east-1 when creating a bucket
2. Ask for a limited access key with a Read or Read/Write/Delete grant on one bucket. A full access key can create, configure and delete every bucket
3. Do the object work through the S3 API. The MCP server and doctl cannot upload, list, move or delete files
4. Retry with exponential backoff on 503 Slow Down, and keep below 800 operations a second per bucket
5. Fetch presigned links from the origin host, not the CDN. The docs say presigned requests through the CDN are not cached and can double the bandwidth charge
6. Avoid many tiny objects. Each bills as at least 4 KiB on Standard and 128 KiB on Cold Storage, which also has a 30-day minimum

Wasabi Hot Cloud Storage

1. Use the bucket's own regional endpoint, such as s3.eu-central-2.wasabisys.com. The docs say a wrong endpoint allows GET but not PUT or DELETE
2. Ask for a sub-user key with a policy limited to one bucket, or an STS session. A root key has full access, billing included
3. Avoid short-lived objects. Each object deleted before 90 days is billed for the remaining days, and objects under 4 KB bill as 4 KB
4. Keep monthly downloads at or below the stored volume, the limit of the free egress policy
5. Call https:// endpoints explicitly. The S3 API also accepts plain HTTP
6. For the MCP beta, type https://mcp.wasabisys.dev/s3 from the page text. The links in the docs table point at a different host