Connect Amazon SES to EonMailer

Once AWS account, sandbox exit, and IAM keys are ready, connect the client’s workspace in EonMailer. Connection is per client workspace — each client can have their own SES account and region.

Prerequisites checklist

• SES production access approved (leave sandbox)
• IAM access key ID and secret (create credentials)
• Chosen AWS region matches where domains will be verified
• Client workspace created in EonMailer
• You have Admin or Integrations permission on that workspace

Step 1 — Switch to the client workspace

1. Open app.eonmailer.com and sign in.
2. Use the workspace switcher in the top bar to select the client (never configure providers in “All clients” view).
3. Navigate to Settings → Email provider (or Sending → Provider depending on your build).

Step 2 — Choose Amazon SES

1. Click Connect provider or Change provider.

2. Select Amazon SES.

3. Enter:

   • AWS region — e.g. us-east-1 (must match SES console region)
   • Access key ID — starts with AKIA…
   • Secret access key — 40-character secret

4. Click Save or Verify connection.

EonMailer performs a lightweight API call (quota/identity check). Green status means credentials and region are valid — not that DNS is complete.

Warning Pasting keys from the wrong region shows as connected but fails at send time with identity errors. Double-check the region dropdown against your SES console URL.

Step 3 — Add the sending domain

1. Still in Settings, open Domains or follow the post-connect prompt.
2. Enter the domain clients will see in From addresses, e.g. mail.clientco.com or clientco.com.
3. EonMailer displays DKIM CNAME records (and sometimes a verification TXT) to publish at DNS.

Copy records exactly — some DNS hosts auto-append the root domain; remove duplicate suffixes if your host warns about FQDN.

Step 4 — Publish DNS and verify

1. Log in to the client’s DNS host (Cloudflare, Route53, GoDaddy, etc.).
2. Add each record EonMailer shows with the given host/name and value.
3. Return to EonMailer and click Verify or wait for automatic polling (usually 5–30 minutes; up to 48 hours globally).

All checks should turn green: Domain verified, DKIM, optionally MAIL FROM if you configure a custom bounce domain.

Detailed DNS guidance: Verify a domain in EonMailer and SPF, DKIM, and DMARC.

Step 5 — Configure event feedback (recommended)

For bounces and complaints to suppress bad addresses automatically:

1. In EonMailer, open Webhooks or the SES setup panel’s Events section.
2. Copy the HTTPS endpoint URL provided.
3. In AWS SES → Configuration sets or Notifications, create an SNS topic / event destination pointing to that URL (exact clicks vary by SES v1 vs v2 UI — follow in-app copy).

Without events, sends work but deliverability dashboards stay empty and suppressions won’t auto-update.

Step 6 — Set default From address

1. Go to Senders or From addresses.
2. Add hello@mail.clientco.com (must match verified domain).
3. Mark as default for campaigns and automations.

SES rejects From domains that aren’t verified.

Step 7 — Send a test email

1. Use Send test email in provider settings, or create a draft campaign to internal staff only.
2. Confirm receipt in inbox (not spam).
3. Check Activity / Message log for Delivered status.

If the message lands in spam during testing, that’s common before warmup — see Send-ready checklist.

Step 8 — Mark send-ready in your runbook

When tests pass and DNS is green, complete the Send-ready checklist before scheduling the client’s first broadcast.

Common connection failures

Error in EonMailer	Fix
Invalid credentials	Regenerate key; watch for copy/paste spaces
Throttling	Sandbox limits or burst — request limit increase
Message rejected: Email address not verified	Still in sandbox or unverified From domain
DKIM fail	CNAME typo or DNS proxy (orange-cloud) breaking DKIM

Full list: Troubleshoot Amazon SES.