Skip to main content

Amazon SES setup

Testimonial Requests Through Amazon SES SMTP

Amazon SES is cheap and dependable, and it starts every new account in a sandbox that will only deliver to addresses you have verified yourself. That is the first thing to know before routing review requests through it. StoryProof can send requests through an SMTP account you control from a paid plan, and SES offers SMTP. The work on the AWS side is a verified domain, production access, and SMTP credentials made for the right Region.

  • Out of the sandbox before a customer is asked
  • SMTP credentials, not your AWS access keys
  • One Region for identity, credentials and endpoint

SES checklist

Get SES ready for real customers

Pick one AWS Region and do everything in it: the identity, the production access request and the SMTP credentials. Most SES surprises come from a step done in a different Region.

Verify your domain
Leave the sandbox
SMTP credentials
StoryProof

Ticks stay in your browser. Nothing is saved or sent.

The problem, solved

SES pitfalls, and what StoryProof contributes

  • Problem 1

    Our whole stack already sends through SES

    A second email vendor for one message type means another bill and another set of DNS records.

  • Problem 2

    The test worked, real requests vanished

    In the sandbox, SES delivers to verified addresses, which is usually just the team. Customers are not on that list.

  • Problem 3

    AWS asks how we handle complaints

    The production access form makes you confirm you only send to people who asked for mail and handle bounces and complaints.

  • Problem 4

    Reminders add to our volume

    Every reminder counts toward your SES quota and your complaint rate.

  • Problem 5

    A plain request opens a plain page

    SES sends exactly what it is given, so the form behind the link has to carry the brand.

Sandbox or production

Source: Amazon SES Developer Guide, “Request production access”, read 2026-11-17.
Sandbox (every new account)Production access
Who you can send toVerified addresses and domains, and the SES mailbox simulatorAny recipient
Volume200 messages per 24 hours, 1 per secondYour account’s own quota
ScopeSeparate per AWS RegionGranted per Region
Use for StoryProofInternal tests onlyRequests to customers

In StoryProof

Set up SES for StoryProof

Step 1 of 5

Create and verify a domain identity

In the SES console for your chosen Region, create a Domain identity with Easy DKIM and publish its three CNAME records.

Before you start

Points to settle first

  • SMTP is the documented route

    StoryProof names SMTP among its providers. This page does not claim a direct SES API connection.

  • Paid plan required

    Sending through your own provider starts at Pro.

  • Production access is AWS’s decision

    AWS reviews each request and may ask for more detail. Nothing here can speed that up.

  • Everything is per Region

    Identities, sandbox status and SMTP credentials all belong to one Region. Credentials from one Region will not work on another Region’s endpoint.

  • Steps follow AWS docs

    The SES steps follow the Amazon SES Developer Guide as read on 2026-11-17 and have not been clicked through on a live account.

FAQ

Questions people ask

Short answers to what usually comes up next.

Can I use my AWS access key as the SMTP password?

No. AWS says the SMTP password is different from the secret access key. Create SMTP credentials on the SES SMTP settings page.

Marketing or transactional on the production access form?

AWS asks for the type that describes most of your mail. Requests to a customer about their own purchase are one-to-one; if SES also sends your newsletters, describe that honestly.

Why did my identity not verify?

AWS lists common causes: values in the wrong DNS fields, a DNS host appending the domain to the name, a missing underscore, or records from another Region. It can take up to 72 hours.

Do I need a custom MAIL FROM domain?

It is optional in SES. Easy DKIM on your domain is the part this page relies on.

Still have a question? Ask the StoryProof team or book a demo.

Send requests through your own SES account

Collect testimonials in StoryProof with requests that leave from your verified domain over Amazon SES.

Sources

  1. Creating and verifying identities in Amazon SES, Amazon SES Developer Guide. Checked 2026-11-17.
  2. Request production access (moving out of the Amazon SES sandbox), Amazon SES Developer Guide. Checked 2026-11-17.
  3. Obtaining Amazon SES SMTP credentials, Amazon SES Developer Guide. Checked 2026-11-17.
  4. Connecting to an Amazon SES SMTP endpoint, Amazon SES Developer Guide. Checked 2026-11-17.

Last updated 2026-11-17.