Amazon SES

Use Amazon SES when you want Drip Drop to send email through your Amazon SES account. This page covers the current connection form, optional tracking and inbound settings, and the checks to make before using the provider in a flow.

  • You already send through AWS and want Drip Drop to use your own Amazon SES account and sending reputation.
  • You want a dedicated email sending service rather than a mailbox-based connection such as Gmail or Outlook.
  • You want SES delivery and engagement events, or inbound replies, routed back into Drip Drop.
  • Have an AWS Access Key ID and AWS Secret Access Key for an AWS identity in that account.
  • Confirm your role can create integrations. Without that permission, New Integration is not shown.
  • For sending, credential validation, and sender sync, allow ses:SendEmail, ses:SendRawEmail, ses:GetAccount, and ses:ListEmailIdentities.
  • For tracking events, also allow ses:GetConfigurationSet, ses:CreateConfigurationSet, ses:GetConfigurationSetEventDestinations, ses:CreateConfigurationSetEventDestination, and ses:UpdateConfigurationSetEventDestination.
  • For the SNS event path, also allow sns:CreateTopic, sns:GetTopicAttributes, sns:SetTopicAttributes, sns:Subscribe, and sns:ListSubscriptionsByTopic.
  • For inbound email, also allow ses:DescribeActiveReceiptRuleSet, ses:DescribeReceiptRuleSet, ses:DescribeReceiptRule, ses:CreateReceiptRuleSet, ses:CreateReceiptRule, ses:UpdateReceiptRule, and ses:SetActiveReceiptRuleSet. The describe and update permissions are required for safe setup reruns and drift reconciliation, even when the first setup only creates resources.
  • Know the AWS Region where your SES identities are verified. The region must match the identities used by this provider.
  • Check whether the SES account still has sandbox access. A sandbox account can only send to addresses verified in SES and is capped at 200 messages a day; request production access in the Amazon SES console before real sends.
  • Choose a safe test contact for the first send.
Choose Amazon SES (Beta) from the New Integration provider list.
  1. Open Integrations → Email.
  2. Choose New Integration and select Amazon SES.
Amazon SES connection form showing the integration name, blank access-key fields, an unselected AWS Region, and the optional Configuration Set field.
  1. Enter a Name for the integration.
  2. Enter the AWS Access Key ID.
  3. Enter the AWS Secret Access Key.
  4. Select the AWS Region.
  5. Optionally enter a Configuration Set. Leave it blank when you want Drip Drop to create one automatically.
  6. Select Save & Continue.
Review the Amazon SES webhook status, configure or verify the webhook, and choose tracking or inbound-email options. The generated webhook URL is hidden for documentation.

On Webhooks, choose the tracking and inbound features you need:

  • Track Clicks
  • Track Opens
  • Enable Inbound Parse

Select Configure Webhook to create or reconcile the SES configuration set, SNS topic, event destination, and HTTPS subscription used for delivery, bounce, complaint, and delay events. Open and click events are included only when their tracking options are enabled. SNS confirms the HTTPS subscription automatically; no manual confirmation is required. Select Save Webhook to continue, or Skip for now to postpone setup. Running Configure Webhook again reuses or updates existing resources instead of creating duplicates.

When Enable Inbound Parse is on, enter a dedicated Reply-To domain such as reply.example.com, not a complete email address. Drip Drop combines the sender’s local part with this domain; for example, [email protected] becomes [email protected]. The inbound domain must be verified as an SES identity, and its MX record must point to the region-specific SES inbound SMTP endpoint shown in the form. Drip Drop does not support inbound messages larger than 150 KB.

How receipt rules are applied: Drip Drop adds a receipt rule to the AWS account’s active rule set. If no rule set is active, Drip Drop creates and activates one; otherwise, it reuses the active set. By default, the rule matches the entire inbound domain so multiple sender addresses can receive replies. SES can deliver the same message to every enabled rule whose recipient condition overlaps. Drip Drop does not stop subsequent customer-managed rules, so inspect the active rule set if inbound messages appear more than once.

Review configured sender identities, verification status, and the default sender before continuing.

On Senders, add at least one email address or select Sync from provider to import the email-address identities returned by SES. A verified SES domain authorizes addresses under that domain, but SES does not enumerate the individual addresses beneath it, so add those sender addresses manually. Select Continue. Use Skip for now only if you plan to finish sender setup later.

Confirm that stored credentials, webhook configuration, and sender identities are present before finishing setup.
  • On Verify, select Check credentials.
  • If you configured webhooks, select Verify webhook.
  • Confirm Senders reports at least one configured sender, resolve any setup warning, then select Done.
  • Send to a safe test contact before using the integration with real contacts.
  • Open the Flow Editor. In the email block, select the integration by its Name under Integration, then select an address under From Email.

If Drip Drop reports that the SES account is in the sandbox, the account can send only to addresses verified in SES and is capped at 200 messages a day. Request production access in the Amazon SES console before using it for real sends.

If Setup Is Interrupted or Unclear

If setup times out or is interrupted, do not assume that AWS made no changes. Before deleting resources or running setup again:

  1. Check the provider’s saved Configuration Set and inbound status.
  2. In the configured AWS Region, inspect the SES configuration set and event destination, SNS topic and HTTPS subscription, active receipt rule set, and Drip Drop receipt rule.
  3. Compare the AWS readback with the saved provider settings.

Run Configure Webhook again only after identifying what must be reconciled. A successful HTTP response alone does not prove that setup completed; confirm both the saved provider state and the corresponding AWS resources.

AWS credentials or Region are rejected
  • Re-enter the AWS Access Key ID and AWS Secret Access Key, then save the provider again.
  • Confirm AWS Region matches the region where the SES identities are verified. The configuration set, SNS topic, and inbound MX target are all region-specific.
The sender is not available
  • Check that the sender identity is verified in the selected SES region.
  • If you use a verified domain, make sure the sender address already exists in Drip Drop before checking its provider status.
The account shows a sandbox warning
  • Send only to SES-verified recipients, or request production access in the Amazon SES console.
  • This is not a Drip Drop credential failure.
Tracking events are missing
  • Confirm Enable Webhooks is on and Configure Webhook completed, so a configuration set and SNS event path are attached.
  • Check that Configuration Set is saved on the provider. Without it, SES attaches no event notifications to the message.
  • Run Configure Webhook again after changing the tracking toggles or Configuration Set. If the AWS Region must change after webhook setup, create a new Amazon SES integration for that region and configure it separately; Configure Webhook does not migrate the saved SNS topic between regions.
Inbound email does not arrive
  • Confirm Enable Inbound Parse is on and Inbound Parse Domain is entered.
  • Confirm the domain is verified in the selected AWS Region and its MX record points to the region-specific SES inbound SMTP endpoint.
  • Inbound messages over 150 KB are not supported.
A send fails after setup
  • Open History and inspect the send error.
  • Confirm the integration is Active, the selected sender is available, and the flow’s email block selects that integration under Integration and an address under From Email.
Configuration keeps failing
  • Check the AWS permissions for SES, SNS, and receipt-rule setup in the selected region.
  • Email — compare provider choices and the shared email flow.
  • Flow Editor — add an email block and select Amazon SES.
  • History — inspect send activity and errors.