Wasabi Hot Cloud

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

  • You already keep objects in Wasabi Hot Cloud Storage and want Drip Drop to read and write in a bucket you already run.
  • You want an S3-compatible bucket that uses a standard access key pair, without opening or managing an AWS account.
  • You want Drip Drop to derive the storage endpoint from the bucket’s region, so there is no endpoint or addressing style to maintain.
  • Confirm you have a Wasabi Hot Cloud Storage bucket and know its Region.
  • Create a Wasabi access key pair with an Access Key ID and a Secret Access Key for the account that can access 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 confine Drip Drop’s stored attachments to a dedicated path in the bucket.

Wasabi shows the Secret Access Key only when you create the key. Copy it then and store it securely.

  1. Open Integrations → Storage.
  2. Select New Integration and choose Wasabi.
Choose Wasabi 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 and select the bucket’s Region.
  4. Optionally enter a Key Prefix. Drip Drop can access only objects beneath it.
  5. Select Save & Continue.
Enter the Wasabi 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 Wasabi endpoint from the Region you select, so the form does not ask for an Endpoint URL, Addressing Style, or Encryption setting. The region must match the bucket’s home region; a mismatch causes signing or object-operation failures. If your region is not in the list, select My region isn’t listed and type it.

The Key Prefix limits stored attachments to that path. Objects outside it are not browsable or attachable. Changing the prefix later does not move existing objects; it changes which stored attachments Drip Drop can access.

  1. On the Verify step, select Check credentials. After the check succeeds, select Done.
  2. Confirm that the integration you named appears as Active on the Storage page.
  3. Open a message template, find Attachments, then select Browse files → Connected storage.
  4. Choose the integration and 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. Credential or permission errors are reported separately from network or Wasabi service errors.

Use https://s3.<region>.wasabisys.com/<bucket-name> as the Public Base URL. Configure a bucket policy that grants anonymous read access only to the Public Folder.

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 region or signature error
  • Confirm the selected Region is the bucket’s home region as shown in the Wasabi console.
  • Drip Drop derives the endpoint from this value, so a mismatch causes signing or object-operation failures rather than a missing-bucket error.
  • If you typed a region with My region isn’t listed, recheck it for typos.
Invalid credentials
  • Confirm the Access Key ID and Secret Access Key are a matching pair from the same Wasabi account and that the key is still enabled.
  • Wasabi shows the secret only when the key is created; if the stored value may be wrong, create a fresh key pair and save the connection again.
Access denied on bucket operations
  • Confirm the Bucket Name is correct and belongs to the account that issued the key pair.
  • Check that the key’s policy allows upload, read, delete, and list on that bucket, including objects beneath the configured Key Prefix.
  • A restricted sub-user can list while being denied object writes; validation tests object access, not just bucket existence.
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; files saved under the previous prefix stop appearing in the attachment library.
  • Uploads made through Drip Drop use automatically generated keys, so look under the prefix rather than a filename you chose.
  • 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.