DigitalOcean Spaces

Connect DigitalOcean Spaces to store and reuse Drip Drop attachments and images in a DigitalOcean Spaces bucket you manage. This guide explains the required credentials, connection settings, and verification steps.

  • You already run infrastructure on DigitalOcean and want Drip Drop’s attachments and images stored on the same account.
  • You want an S3-compatible bucket whose endpoint follows the datacenter region, so there is no endpoint URL to enter or maintain.
  • You want a Spaces access key pair scoped to the team that owns the bucket rather than credentials from a separate storage vendor.
  • Confirm you have a DigitalOcean Spaces bucket and know its Datacenter Region (for example, nyc3).
  • Generate a Spaces Access Key ID and Secret Access Key for the account that can reach the bucket.
  • Confirm the key pair allows the bucket operations Drip Drop needs: upload, read, delete, and list.
  • Confirm your role can create integrations. Without that permission, New Integration is not shown.
  • Optionally decide on a Key Prefix to keep Drip Drop’s attachments and images under a dedicated path.

DigitalOcean Spaces authenticates with an Access Key ID and Secret Access Key pair rather than a single API key, so both halves are required before the connection can be saved.

  1. Open Integrations → Storage.
  2. Select New Integration and choose DigitalOcean Spaces.
Choose DigitalOcean Spaces in the integration wizard.
  1. Review or change the Name.
  2. Enter your Access Key ID and Secret Access Key.
  3. Enter the Bucket Name.
  4. Select the bucket’s Datacenter Region.
  5. Optionally enter a Key Prefix to keep Drip Drop’s attachments and images under a dedicated path.
  6. Select Save & Continue.
Enter the DigitalOcean Spaces connection settings, then select Save & Continue. The example-invalid-bucket name is deliberately nonfunctional, and docs-example-only is an illustrative key prefix.

Drip Drop derives the Spaces endpoint from the Datacenter Region you select: https://<region>.digitaloceanspaces.com. The form does not ask for an Endpoint URL, Addressing Style, or Encryption setting. The region must match the datacenter where the Space lives. A mismatch causes signing or object-operation failures.

Drip Drop reads and writes only beneath the configured Key Prefix, and uploaded files are stored there under automatically generated keys. Changing the prefix later does not move existing objects; it changes the boundary that Drip Drop can browse and attach from.

  1. On the Verify step, select Check credentials. After the check succeeds, select Done.
  2. Confirm that DigitalOcean Spaces appears as Active on the Storage page.
  3. Open a message template, find the Attachments section, then select Browse files → Connected storage.
  4. Choose the integration you named, select an object beneath the configured Key Prefix, then select Attach.

When Drip Drop validates the connection, it confirms bucket access by creating, reading, and deleting a temporary object beneath the configured Key Prefix. A successful result means the credentials can reach the bucket and perform the operations Drip Drop needs.

Use the Space’s origin or CDN endpoint from its Settings tab as the Public Base URL. The CDN endpoint is preferred for email images, for example https://<space-name>.<region>.cdn.digitaloceanspaces.com.

Images embedded in emails must remain publicly readable without signing in. Keep public access limited to a folder that is separate from the private attachment prefix.

  1. Open the saved integration and expand Serve email images from this bucket.
  2. Enter the Public Base URL and a separate Public Folder.
  3. Configure your storage service to allow anonymous read access to the Public Folder.
  4. Select Verify public access.
  5. After Publicly readable appears, enable Available as a public media location.
  6. Return to Storage. Under Email image location, choose the verified bucket.

If connection or public-media settings change, verification becomes stale. Select Verify public access again before using the bucket.

Changing Email image location affects only newly published images. Existing published images stay at their original location.

Wrong Datacenter Region or signature error
  • Confirm the selected Datacenter Region is the datacenter the Space actually lives in (for example, nyc3).
  • Drip Drop derives the endpoint from this value, so a mismatch causes signing or object-operation failures.
  • If the Space’s datacenter is not in the list, use My region isn’t listed and enter the datacenter code exactly as DigitalOcean shows it.
Invalid or insufficient credentials
  • Confirm both the Access Key ID and the Secret Access Key belong to the DigitalOcean account that can reach the bucket.
  • Generate a fresh Spaces key pair if the secret may be wrong or was not captured when it was created, then save the connection again.
Bucket access fails
  • Confirm the Bucket Name matches the Space exactly; it must not include the datacenter host.
  • Check that the credentials can inspect the bucket and upload, read, and delete objects beneath the configured Key Prefix.
  • Validation tests object access rather than only checking that the bucket exists, so listing can succeed while object operations fail.
A file is not visible under the Key Prefix
  • Confirm the object is beneath the configured Key Prefix. Drip Drop cannot browse or attach anything outside it.
  • Changing the prefix does not move existing objects; point it back at the original path or re-upload.
  • Uploads made through Drip Drop use automatically generated keys, so look under the prefix rather than the bucket root.
  • Storage: choose and manage storage for Drip Drop attachments and images.
  • Message Templates: add stored files as attachments or use them as images in email designs.