Configuring DigitalOcean Spaces with quickS3

DigitalOcean Spaces is S3-compatible object storage that sits inside the rest of the DigitalOcean ecosystem. quickS3 gives it a dedicated connection form: you pick a region and enter your credentials, quickS3 works out the endpoint for you, and your team gets secure access to Spaces without setting up CORS by hand.

Why DigitalOcean Spaces?

If you already run Droplets or App Platform, the appeal is mostly that it’s right there: same account, same billing, no new vendor to set up. Pricing is predictable and often lands below the big clouds, and since it speaks the S3 API it works with standard S3 tooling and with quickS3’s access control, audit log, and browser upload/download flows. Spaces are available in regions across North America, Europe, and Asia-Pacific, so you can keep data close to your users.

Step 1: Create a Space and API key

1. Log in to the DigitalOcean Control Panel
2. Go to Spaces in the sidebar and click Create Space
3. Choose a region (e.g. nyc3, sfo3, ams3) and a unique Space name
4. Create a Spaces access key (or reuse an existing one): go to API → Spaces Keys → Generate New Key, give it a name, and copy the Access Key and Secret Key. You won’t see the secret again.

Step 2: Add DigitalOcean Spaces in quickS3

1. In quickS3, go to Storage Providers and click Add Provider.
2. Choose DigitalOcean Spaces.
3. Fill in the form:
   • Region is where your Space lives (e.g. nyc3, ams3, sfo3). Type the region code or pick one from the suggestions. quickS3 shows and uses the correct endpoint for that region, so you don’t enter an endpoint URL yourself.
   • Bucket scopes (optional): leave blank to let quickS3 list every Space the key can reach. If the key can’t list Spaces, enter a comma-separated list of names (e.g. assets, backups).
   • Access key ID and Secret key come from Step 1.
4. Leave Allow quickS3 to update bucket CORS settings (recommended) on. When you save or test the connection, quickS3 adds the quicks3.com origin to your Space’s CORS policy so browser uploads work.
5. Save. quickS3 validates the connection, and then you can assign Spaces to roles and start using them.

How quickS3 picks the Spaces endpoint

quickS3 builds the endpoint from the Region you choose:

• Endpoint: https://<region>.digitaloceanspaces.com (e.g. https://nyc3.digitaloceanspaces.com)

So you only need to know your Space’s region; the endpoint is set automatically. Supported regions include nyc1, nyc2, nyc3, ams3, sfo2, sfo3, sgp1, lon1, fra1, tor1, blr1, syd1, and atl1.

Troubleshooting

Access denied or signature errors

• Confirm the Spaces key has read/write access to the Space
• Check that the region matches the one where you created the Space
• If you use bucket scopes, make sure the Space name is in the list

Browser says “CORS policy blocked”

• Keep Allow quickS3 to update bucket CORS settings on and run Test connection again so quickS3 can add the quicks3.com origin
• If you manage CORS yourself, allow https://quicks3.com with methods GET, PUT, HEAD, DELETE and the appropriate headers

---

Ready to try it? Sign up for quickS3 and connect your DigitalOcean Space.