DocsSet up sending

Amazon SES

Connect your own Amazon SES account with a narrowly scoped IAM key, then leave the SES sandbox.

Connect step by step

Each newsletter has its own SES credentials. Open Settings → Sending and work through the checklist; each step unlocks the next, and only owners can change it.

  1. Credentials
    An IAM access key ID (it starts with AKIA), its 40-character secret and a region. Temporary ASIA keys are rejected because they expire. The secret is encrypted with AES-256-GCM the moment it arrives and is never shown again.
  2. Account probe
    Reads whether the account is in the sandbox, has production access, or has sending disabled.
  3. Quota
    Reads your 24-hour sending quota and maximum send rate. Both are refreshed every six hours, before every campaign, and whenever you press Refresh.
  4. Configuration set
    Creates a configuration set named newsletter-sh-{slug} with reputation metrics on, an SNS topic, and an event destination for sends, deliveries, bounces, complaints, rejects, rendering failures and delays. The subscription to your newsletter's private endpoint is confirmed automatically, and every SNS message's signature is checked.
  5. Domain
    Verifies your sending domain with Easy DKIM and sets a custom MAIL FROM subdomain. The page shows the records and checks SES every 30 seconds for ten minutes after you publish them. See Domain authentication.
  6. Test send
    Sends a real email to your own account address through the full pipeline. Campaigns unlock only after it succeeds. While you are in the sandbox, the recipient must be an address verified in SES.

IAM policy

Create a dedicated IAM user for newsletter.sh with only this policy attached. The SNS statement is limited to topics whose names start with newsletter-sh-.

newsletter-sh-policy.jsonJSON
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "ses:SendEmail",
        "ses:SendRawEmail",
        "ses:GetAccount",
        "ses:GetSendQuota",
        "ses:CreateEmailIdentity",
        "ses:GetEmailIdentity",
        "ses:PutEmailIdentityMailFromAttributes",
        "ses:CreateConfigurationSet",
        "ses:GetConfigurationSet",
        "ses:CreateConfigurationSetEventDestination",
        "ses:UpdateConfigurationSetEventDestination",
        "ses:PutSuppressedDestination",
        "ses:ListSuppressedDestinations"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "sns:CreateTopic",
        "sns:Subscribe",
        "sns:GetTopicAttributes"
      ],
      "Resource": "arn:aws:sns:*:*:newsletter-sh-*"
    }
  ]
}

Creating the key

  • In the AWS console, open IAM → Users → Create user. It does not need console access.
  • Attach the policy above as an inline or customer-managed policy.
  • Open the user, then Security credentials → Create access key, and choose “Application running outside AWS”.
  • Paste the key ID and secret into newsletter.sh. You won't need the secret again.

Regions and quota

Pick the SES region your account is set up in. These 21 regions are supported:

us-east-1us-east-2us-west-1us-west-2ca-central-1eu-west-1eu-west-2eu-west-3eu-central-1eu-north-1eu-south-1ap-south-1ap-northeast-1ap-northeast-2ap-northeast-3ap-southeast-1ap-southeast-2sa-east-1me-south-1af-south-1il-central-1

A campaign that needs more than your remaining 24-hour quota is blocked before it starts, with the numbers shown. If the quota runs out mid-send, the campaign pauses and tries again an hour later.

Leaving the SES sandbox

New SES accounts start in the sandbox, where mail only reaches verified addresses. Campaigns stay blocked until AWS grants production access. Request it in the SES console under Account dashboard → Request production access.

The Sending page prepares the request text for you, filled in with your newsletter's name, signup page, archive and settings. AWS wants to know:

  • Your use case: an opt-in newsletter, how often you send and roughly how much.
  • How people opt in: your hosted or embedded signup form, with double opt-in confirmation if it is on.
  • How bounces and complaints are handled: events flow back through SNS, hard bounces and complaints are suppressed permanently and mirrored into your SES account suppression list.
  • How people unsubscribe: a one-click List-Unsubscribe header on every email, plus a footer link next to your postal address.

Send rate and shared accounts

  • Campaigns send at up to 80% of your SES maximum send rate, leaving headroom for anything else on the account.
  • Several newsletters can share one AWS account. Newsletters with the same access key share one rate limiter, so together they never exceed what SES allows.
  • Mail goes out in small batches that resume where they stopped after any interruption, so nobody gets the same issue twice.
  • If SES rejects the credentials mid-send (for example, the key was deleted), sending pauses and the campaign can be resumed once the key is fixed.
newsletter.sh

Newsletters on your own sending account. Invite-only, sent through Amazon SES or the provider you already use.

© 2026 newsletter.sh