Amazon S3

Connect Amazon S3 to store and reuse Drip Drop attachments and images in an S3 bucket you manage. This guide explains the required AWS credentials, connection settings, and verification steps.

  • You already use AWS and want Drip Drop’s attachments and images stored in a bucket you manage.
  • You want Drip Drop to use the standard AWS endpoint derived from the AWS Region you select, without asking for a custom endpoint.
  • You want Drip Drop to browse, upload, and manage objects only beneath a dedicated Key Prefix.
  • Confirm you have access to an Amazon S3 bucket and know its AWS Region.
  • Have an Access Key ID and Secret Access Key for an AWS identity that can access the bucket.
  • Confirm the credentials allow PutObject, GetObject, and DeleteObject for objects in the bucket, and ListBucket for the bucket itself.
  • Confirm your role can create integrations. Without that permission, New Integration is not shown.

Use credentials that can access the selected bucket, and make sure the bucket name and AWS Region match. Each Amazon S3 integration connects to one bucket, so choose the bucket Drip Drop should use for attachments and images.

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

Amazon S3 uses the standard AWS endpoint for the AWS Region you select. Unlike the S3-Compatible Storage integration, it does not require an Endpoint URL, Addressing Style, or Encryption setting.

Optionally use a Key Prefix to keep Drip Drop attachments and images separate from other objects in the bucket. When provided, Drip Drop normalizes the prefix and rejects path traversal or object keys outside the configured boundary.

  1. On the Verify step, select Check credentials. After the check succeeds, select Done.
  2. Confirm that Amazon S3 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.

Files selected from Amazon S3 remain associated with that integration. Selecting an existing object uses the file in place; uploading a new email attachment or image for an email template creates a new object beneath the configured Key Prefix.

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 AWS service errors.

Drip Drop generates the object key for each uploaded file and keeps it within the configured Key Prefix. You cannot provide a custom object key for an upload. The Connected storage tab lists the objects available beneath the prefix.

If an object is not visible, confirm that it is in the selected bucket and beneath the configured Key Prefix. Changing the prefix changes which objects Drip Drop can browse and select, but it does not move existing objects. The prefix defines a storage boundary; it does not copy or relocate files.

Amazon S3 appears as Active in Storage Integrations.

Use your bucket’s website or REST endpoint, or a CloudFront domain in front of it, as the Public Base URL. For a standard regional REST endpoint, use https://<bucket-name>.s3.<region>.amazonaws.com. Configure the bucket policy to allow anonymous s3:GetObject access only to the Public Folder, and ensure Block Public Access permits that policy.

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.

Validation fails
  • Recheck the Access Key ID, Secret Access Key, Bucket Name, and Region.
  • Confirm the credentials allow PutObject, GetObject, DeleteObject, and ListBucket.
A file is not visible
  • Confirm the file is in the selected bucket and beneath the configured Key Prefix.
An AWS request fails
  • Recheck the Region and credentials before changing the Key Prefix.
  • 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.