Migrate from Amazon SES to Sendix

Trade IAM-signed requests and SNS or EventBridge pipelines for a Bearer-key JSON API, signed webhooks and a dashboard with logs, templates and domain checks.

Start sending free Read quickstart

No IAM or SigV4 signing
Webhooks instead of SNS
Per-message event history
Suppression import

Last reviewed September 12, 2026

smtp migration

drop-in

.envAmazon SES → Sendix

- SMTP_HOST=email-smtp.eu-west-1.amazonaws.com+ SMTP_HOST=smtp.sendix.dev- SMTP_PORT=587+ SMTP_PORT=587  # STARTTLS- SMTP_USER=AKIA••••••••+ SMTP_USER=<username from dashboard>- SMTP_PASS=••••••••+ SMTP_PASS=<Sendix API key>

DNSSMTP / APIWebhooks

Short answer

How do I migrate from Amazon SES to Sendix?

Verify your domain in Sendix, then change SMTP from email-smtp.<region>.amazonaws.com and your IAM-derived SMTP credentials to smtp.sendix.dev:587 with a Sendix API key, or replace SESv2 SendEmail calls (AWS Signature Version 4) with a JSON POST to https://sendix.dev/api/v1/emails using a Bearer key. Replace configuration-set event destinations (SNS, EventBridge, Firehose) with Sendix webhooks and import your account-level suppression list.

Migration plan

Four steps, no big-bang cut-over.

Run Amazon SES and Sendix side by side until the new path is proven.

01
DNS
Add and verify your domain
Publish the Sendix DKIM TXT record (<selector>._domainkey), the bounce CNAME (bounce.<your-domain> → bounce.sendix.dev) and add include:mail.sendix.dev to your SPF record. Amazon SES’s DKIM records can stay while both providers send.
02
SMTP or API
Point sending at Sendix
SMTP users swap the regional endpoint and IAM-derived credentials. API users replace the AWS SDK SendEmail call with an HTTPS POST: Content.Simple becomes subject, html and text, and Content.Template becomes template_id with template_data.
03
events
Recreate your webhooks
Create a Sendix webhook for the events you consumed from Amazon SES, verify X-Sendix-Signature, and map event names with the table below.
04
suppressions
Import suppressions, then cut over
Export bounced, unsubscribed and complained addresses from Amazon SES, add them with POST /v1/suppressions, move traffic gradually, then remove Amazon SES’s SPF include.

Concept map

Amazon SES → Sendix, side by side.

Where each piece of your current integration lives in Sendix.

Concept	Amazon SES	Sendix
SMTP server	Amazon SESemail-smtp.<region>.amazonaws.com:587	Sendixsmtp.sendix.dev:587 (STARTTLS)
SMTP login	Amazon SESSMTP credentials derived from an IAM user	SendixUsername from your dashboard, API key as password
Send endpoint	Amazon SESSESv2 SendEmail (AWS SDK or HTTPS)	SendixPOST https://sendix.dev/api/v1/emails (JSON)
API authentication	Amazon SESAWS Signature Version 4 (IAM)	SendixAuthorization: Bearer <API key>
Templates	Amazon SESSES templates ({{placeholder}} syntax)	SendixVersioned {{variable}} templates (template_id + template_data)
Delivered event	Amazon SESDelivery	Sendixemail.delivered
Bounce event	Amazon SESBounce	Sendixemail.bounced
Complaint event	Amazon SESComplaint	Sendixemail.complained
Webhook security	Amazon SESSigned SNS messages, or EventBridge / Firehose	SendixX-Sendix-Signature (HMAC-SHA256)
Suppressions	Amazon SESAccount-level suppression list	SendixSuppression list API (/v1/suppressions)

Amazon SES is a trademark of its owner. Its column summarizes public documentation as of September 12, 2026; confirm current details in Amazon SES’s docs before migrating.

Before you switch

What to check in your setup.

Amazon SES features that need a plan, and where they land in Sendix.

Event pipeline

There is no SNS or queue plumbing to run: Sendix posts signed webhooks and keeps each message’s events at GET /v1/emails/{id}/events.

Cost at very high volume

SES is priced per message and can be cheaper at very high volume. Compare your volume with Sendix plans on the pricing page.

Sandbox and quotas

SES accounts start in a sandbox with sending quotas; Sendix limits are defined by your plan and shown on the pricing page.

Operations surface

Sendix includes delivery logs, a template editor, domain checks and webhook delivery replay in its dashboard.

FAQ

Frequently asked questions

Answers for teams moving from Amazon SES.

Why move from SES to a managed email API?

Teams usually move for the surrounding tooling rather than raw sending: a JSON API without request signing, webhooks without SNS or EventBridge, and logs, templates and domain verification in one dashboard. At very high volume SES can cost less per message, so compare against your own numbers.

Can I run Amazon SES and Sendix at the same time?

Yes. Each provider signs with its own DKIM selector, and a single SPF record can include both during the transition — keep it to one SPF record and within the 10-DNS-lookup limit. A domain can have only one DMARC record, so keep your existing one if it already has a policy.

Is there a Sendix SDK I can install?

The Node SDK and CLI exist as source packages but are not yet published to npm, so most teams integrate over the REST API (plain HTTPS and JSON) or SMTP. Neither needs an extra dependency.

What happens to addresses that bounced with my old provider?

Import them as suppressions with POST /v1/suppressions and a reason of hard_bounce, unsubscribed or complained. Sendix then reports email.suppressed instead of sending to those addresses.

Free to start

Try it on the free plan, keep the same integration as you grow.

The free plan includes 1,000 emails per month. Paid plans change volume and limits, not your API calls or SMTP settings.

Create free account Compare plans

Ready to send your first email?

1,000 emails free every month. No credit card required. Upgrade only when you outgrow the free tier — and we will let you know when that time comes.

Create free account Talk to sales

Managed SaaS platform · Native SMTP engine · SOC 2 in progress

Migrate from Amazon SES to SendixText underline