HomeDocsQuickstart

Quickstart

This guide walks you through the full setup — from creating an account to sending your first campaign. Most users complete it in under 30 minutes. The only pre-requisite is an active AWS account.

No AWS account yet? Create one at aws.amazon.com. You need a credit card on file, but the free tier covers the first 62,000 emails/month when sending from an EC2 instance, and you only pay SES rates after that ($0.10 per 1,000 emails).
1

Create your SES Mailbox account

Go to app.sesmailbox.com/register and sign up with your email address. Verify your email via the confirmation link we send, then log in.

You start on the Free plan — no credit card required. The Free plan lets you send 1 campaign per month with unlimited contacts, which is enough to get through this quickstart.

2

Create an IAM user and connect AWS SES

SES Mailbox sends email through your own AWS account. You need to create an IAM user with SES permissions and paste the credentials into SES Mailbox.

Create the IAM user in AWS

  1. Open the AWS console → search IAM → Users → Create user
  2. Username: sesmailbox (or anything you like)
  3. Select Attach policies directlyCreate policy
  4. Switch to the JSON tab and paste the policy below
  5. Name the policy SESMailboxPolicy and create it
  6. Attach the policy to the user and create the user
  7. On the final screen, click Create access key → use case: Third-party service → copy the Access Key ID and Secret Access Key
{
  "Version": "2012-10-17",
  "Statement": [{
    "Effect": "Allow",
    "Action": [
      "ses:SendEmail",
      "ses:SendRawEmail",
      "ses:GetSendQuota",
      "ses:GetSendStatistics",
      "ses:VerifyDomainIdentity",
      "ses:VerifyDomainDkim"
    ],
    "Resource": "*"
  }]
}

Paste credentials into SES Mailbox

  1. In SES Mailbox, go to Settings → AWS Credentials
  2. Enter your Access Key ID, Secret Access Key, and AWS region (e.g. us-east-1)
  3. Click Test connection — we'll verify the credentials and fetch your sending quota
Which region? Use the region closest to your users. Most US businesses use us-east-1. European businesses often use eu-west-1 (Ireland). You can change this later, but your verified domains and sending history stay in the original region.
3

Verify your sending domain

To send email from @yourcompany.com, AWS needs to confirm you own the domain. SES Mailbox generates the DNS records — you add them to your DNS provider (Cloudflare, Route 53, Namecheap, etc.).

  1. In SES Mailbox: Settings → Sending Domains → Add Domain
  2. Enter your domain and click Generate records
  3. Add the SPF TXT record, three DKIM CNAME records, and the DMARC TXT record to your DNS
  4. Click Check verification — DNS propagation usually takes 5–30 minutes, sometimes up to 24 hours

See the full Domain Verification guide for exact record values and troubleshooting.

4

Import your subscribers

Go to Contacts → Import CSV. Your CSV needs at minimum an email column. Optional columns: first_name, last_name, and any custom fields you want to use for personalisation.

email,first_name,last_name,plan
ada@example.com,Ada,Lovelace,pro
grace@example.com,Grace,Hopper,free

Column headers are flexible — SES Mailbox auto-detects common patterns (email, EMAIL, Email Address, etc.) and lets you manually map any column.

Migrating from Mailchimp or another ESP? Import your unsubscribe and bounce lists as suppressions before importing active contacts. See the Suppression list guide.
5

Send your first campaign

  1. Go to Campaigns → New Campaign
  2. Choose a name (internal only), subject line, and from address
  3. Write your email in the HTML editor or paste raw HTML
  4. Select your recipient list (or a segment)
  5. Click Send test to preview in your inbox
  6. Click Send campaign to send to all recipients

After sending, the Analytics tab shows opens, clicks, bounces, and unsubscribes — usually updating within a few minutes of delivery.

New AWS account? AWS SES starts in sandbox mode — you can only send to verified email addresses. Request production access to send to anyone. See Getting production access.