---
title: "Migrating from Amazon SES"
description: "OneSend has no SES-compatible endpoint: SES requests are signed with AWS Signature Version 4, so the SDKs cannot simply be pointed at another host."
url: https://onesend.email/docs/migrate/amazon-ses/
---
# Migrating from Amazon SES

OneSend has no SES-compatible endpoint: SES requests are signed with AWS Signature Version 4, so the SDKs cannot simply be pointed at another host. Change the send call to `POST /v1/emails` (or an SDK), or point SMTP clients at OneSend's SMTP ingress. You can keep SES as a provider: connect it under **Sending providers** with an access key, secret and region. The IAM user needs permission to send (`ses:SendEmail`) and, for domain setup, to manage identities.

## Field mapping

SES v2 `SendEmail` to `POST /v1/emails`:

| SES | OneSend | Notes |
|---|---|---|
| `FromEmailAddress` | `from` | |
| `Destination.ToAddresses`, `CcAddresses`, `BccAddresses` | `to`, `cc`, `bcc` | At most 100 recipients per email. |
| `ReplyToAddresses` | `replyTo` | |
| `Content.Simple.Subject.Data` | `subject` | |
| `Content.Simple.Body.Html.Data`, `Text.Data` | `html`, `text` | |
| `Content.Simple.Headers` | `headers` | |
| `Content.Simple.Attachments` | `attachments` | |
| `Content.Raw` (MIME) | not supported over the API | Send raw MIME through SMTP ingress instead. |
| `Content.Template` (`TemplateName`, `TemplateData`) | `template`, `variables` | Recreate the template in OneSend. SES templates use Handlebars; OneSend's `{{variable}}` syntax is similar for simple variables. |
| `EmailTags` (`Name`/`Value`) | `tags` (`name:value`) or `metadata` | |
| `ConfigurationSetName` | `policy` (routing policy), tags | Event destinations are replaced by OneSend webhooks. |
| `ListManagementOptions` | `type: "broadcast"` | OneSend adds one-click List-Unsubscribe and honors unsubscribes. |
| `SendBulkEmail` | `POST /v1/emails/batch` (up to 100) or campaigns | |

```ts
// before (AWS SDK v3)
await ses.send(new SendEmailCommand({ FromEmailAddress: 'hello@acme.dev', Destination: { ToAddresses: ['ada@example.com'] }, Content: { Simple: { Subject: { Data: 'Hello' }, Body: { Text: { Data: 'Hi' } } } } }));

// after (TypeScript SDK in packages/sdk)
await onesend.emails.send({ from: 'hello@acme.dev', to: 'ada@example.com', subject: 'Hello', text: 'Hi' });
```

Apps that use the SES SMTP interface (`email-smtp.<region>.amazonaws.com`) change host, port and credentials to OneSend's SMTP ingress; see [Gmail SMTP](https://onesend.email/docs/migrate/gmail-smtp/#smtp-settings) for the settings.

## Events and suppressions

- SES event publishing (SNS, EventBridge, Firehose) is replaced by OneSend webhooks for your app. For OneSend to receive SES delivery, bounce and complaint events itself, set a configuration set on the SES connection and publish its events to an SNS topic with an HTTPS subscription to the connection's `webhookUrl` (from `GET /v1/connections/{id}`); OneSend confirms the subscription.
- Export the SES account-level suppression list (`ListSuppressedDestinations`, reasons `BOUNCE` and `COMPLAINT`) and import it as described in the [cutover checklist](https://onesend.email/docs/migrate/#general-cutover-checklist). Keep the SES suppression list on: it still protects the SES connection.

## DNS

Keep the Easy DKIM CNAMEs (`<token>._domainkey`) and the custom MAIL FROM subdomain (MX and SPF on, for example, `mail.acme.dev`). With a custom MAIL FROM, your root SPF does not need `include:amazonses.com`. Add the `_onesend-verify` TXT record. If the account is still in the SES sandbox, it can send only to verified addresses until AWS grants production access.

Then follow the [general cutover checklist](https://onesend.email/docs/migrate/#general-cutover-checklist).
