How to set up Amazon SES — step by step
Create, authenticate and approve an Amazon SES account before connecting it to MailBuddy.
What you will need
- An Amazon Web Services (AWS) account owned by your business.
- Access to your domain’s DNS records through Cloudflare, your hosting company or domain provider.
- An email address on the domain you will send from.
- Your business website, postal address and a clear explanation of how subscribers consent to marketing.
- Administrator access to your MailBuddy workspace.
Need help? MailBuddy can assist with the Amazon SES, DNS and MailBuddy connection setup for an additional cost. Contact MailBuddy support for a quote. You or your developer will still need to authorise access to the relevant accounts; never send passwords or AWS secret keys by email.
Step 1: Sign in to AWS and choose the correct region
- Sign in to the AWS Management Console.
- Search for Amazon Simple Email Service or SES.
- Use the region selector at the top of AWS to choose the region you will use with MailBuddy. For UK businesses, Europe (London) — eu-west-2 is normally the clearest choice.
- Keep this same region selected throughout the setup.
SES identities, sandbox status, production approval, quotas and credentials are region-specific. Setting up the domain in one region and entering another region in MailBuddy will cause the connection or sending test to fail.
Step 2: Create your sending-domain identity
- In Amazon SES, open Configuration → Identities.
- Choose Create identity.
- Select Domain and enter your root domain without
https://,wwwor a trailing slash—for example,example.co.uk. - Leave Easy DKIM enabled. The standard 2048-bit DKIM option is recommended.
- You normally do not need to assign a configuration set or tenant during initial MailBuddy setup.
- Choose Create identity.
Step 3: Add the DKIM records to your DNS
- SES will display three DKIM CNAME records.
- Open your DNS provider in another tab.
- Add all three records using the exact Name and Value supplied by SES. Do not add an extra underscore or manually change
._domainkey. - If you use Cloudflare, keep each SES DKIM CNAME set to DNS only, not proxied.
- Save the records and return to SES.
Some DNS providers automatically append your domain name. If yours does, enter only the host portion shown by that provider. DNS verification can be quick, but AWS advises that it may take up to 72 hours.
Step 4: Add a DMARC record
Add a TXT record for _dmarc.yourdomain.co.uk. A sensible monitoring policy while setting up is:
v=DMARC1; p=none;
Only one DMARC record should exist for the same hostname. You can strengthen the policy later after confirming legitimate mail passes DKIM or SPF alignment.
Step 5: Configure a custom MAIL FROM domain
This step is optional, but recommended for clearer SPF alignment and professional sending authentication.
- In SES, open your verified domain identity.
- Find Custom MAIL FROM domain and choose Edit.
- Use a dedicated subdomain such as
bounce.yourdomain.co.ukormail.yourdomain.co.uk. Do not use a subdomain already used for a website or normal inboxes. - Choose Use default MAIL FROM domain as the behaviour on MX failure while initially configuring it.
- Save the setting and copy the MX and TXT records provided by SES into your DNS.
The MX record content must be the regional SES feedback hostname—not an IP address. For Europe (London), it will normally resemble feedback-smtp.eu-west-2.amazonses.com. Use the priority supplied by SES, normally 10. SES requires exactly one MX record on the custom MAIL FROM hostname.
The custom MAIL FROM TXT record normally contains:
v=spf1 include:amazonses.com -all
Do not create two SPF TXT records on the same hostname. If an SPF record already exists there, it must be combined correctly rather than duplicated.
Step 6: Wait for the identity to verify
- Return to SES → Configuration → Identities.
- Open the domain and check that Identity status is Verified.
- Confirm that DKIM shows Successful.
- If custom MAIL FROM is enabled, confirm that it also shows Successful.
If verification remains pending, check the records at the authoritative DNS provider. Adding records inside a cPanel zone that does not control the domain’s nameservers will not affect public DNS.
Step 7: Request production access
- Open the SES Account dashboard while still in the correct region.
- Choose Request production access or open the setup page shown in the sandbox notice.
- Select Marketing if MailBuddy will primarily send newsletters, promotions, competition updates or campaigns.
- Enter your genuine business website.
- Explain your expected sending frequency and volume, how subscribers opt in, how old or inactive data is removed, and how bounces, complaints and unsubscribe requests are handled.
- Confirm that you will comply with the AWS Acceptable Use Policy and submit the request.
A useful description should be specific to the business. For example:
We will send permission-based marketing emails to customers who explicitly opted in through our WordPress website. We expect to send [frequency and approximate volume]. Purchased, rented and scraped lists are not used. MailBuddy provides a one-click unsubscribe link and suppresses unsubscribed recipients. Amazon SES bounce and complaint feedback is processed so affected addresses are suppressed from future campaigns. We regularly clean inactive and invalid contacts and will begin with our most engaged subscribers.
Production approval is separate for each AWS region. While in the sandbox, SES generally allows sending only to verified recipients and applies low daily and per-second limits. Do not launch a live campaign until production access is approved.
Step 8: Create restricted API credentials for MailBuddy
MailBuddy’s recommended Direct Amazon SES API connection needs an AWS Access Key ID and Secret Access Key. These are not the same as SES SMTP credentials.
- Open AWS IAM → Users and create a dedicated user, for example
mailbuddy-ses-sender. - Grant only the SES sending permissions MailBuddy requires:
ses:SendEmailandses:SendRawEmail. - Restrict the policy to your verified SES identity where practical.
- Open the new IAM user, choose Security credentials → Create access key, and select the option for an application running outside AWS.
- Copy the Access Key ID and Secret Access Key immediately. AWS only displays the secret once.
Do not use the AWS root user and do not give MailBuddy broad administrator permissions. If a key is exposed, deactivate it in IAM, create a replacement and update MailBuddy.
Step 9: Connect Amazon SES to MailBuddy
- Sign in to your MailBuddy workspace.
- Open MailBuddy → Settings.
- Select Direct Amazon SES API.
- Enter the exact AWS region used during setup—for example,
eu-west-2. - Paste the IAM Access Key ID and Secret Access Key.
- Enter a From name, a From email address on the verified domain, a reply-to email and your business postal address.
- Leave Configuration set blank unless one has deliberately been created in SES.
- Save the settings.
Step 10: Send and check a test email
- Use MailBuddy’s test-send option and send to an address you control.
- If SES is still in the sandbox, the recipient address must also be verified in that SES region.
- Check the inbox and spam folder.
- Confirm the From name, From email and reply-to address are correct.
- Inspect the message authentication results and confirm DKIM passes. If custom MAIL FROM is configured, confirm SPF also passes.
If MailBuddy reports an authorisation error for ses:SendEmail or ses:SendRawEmail, update the IAM policy for the dedicated MailBuddy user. If it reports an identity error, check that the From domain is verified in the same region entered in MailBuddy.
Step 11: Protect your reputation before the first campaign
- Import only subscribers with a valid lawful basis for marketing.
- Keep unsubscribed, complained and hard-bounced recipients suppressed.
- Start with your most recent and engaged contacts rather than sending to an old list at once.
- Use an accurate From name and subject line, include your postal address and keep MailBuddy’s unsubscribe link intact.
- Monitor SES sending, bounce and complaint metrics after every campaign.
- Increase volume gradually on a new SES account or newly authenticated domain.
Optional managed setup
If you would prefer not to complete the AWS, DNS and MailBuddy configuration yourself, we can assist with setup for an additional cost. This can include guiding you through the AWS account, creating the SES identity, preparing the required DNS records, helping with the production-access request, creating restricted credentials, connecting MailBuddy and completing a test send. Contact MailBuddy support for availability and a quote.
Amazon makes the final decision on production access. Paid setup assistance cannot guarantee that AWS will approve an application, but it can help ensure the technical configuration and information supplied are complete.