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.
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.
How StoryProof solves it
From Pro, review requests can leave from your own domain through your own SMTP account, and SES provides one.
- 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.
How StoryProof solves it
Request production access in the Region you send from, and test with an unverified address before asking customers through StoryProof.
- 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.
How StoryProof solves it
Contacts and smart lists are on every plan, so requests go to recent customers you chose rather than an old list that bounces.
- Problem 4
Reminders add to our volume
Every reminder counts toward your SES quota and your complaint rate.
How StoryProof solves it
From Pro, follow-ups stop once a customer leaves a testimonial, skip people who unsubscribed and send only inside your quiet hours.
- 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.
How StoryProof solves it
Brand settings put your logo and colors on every form, wall and widget, on every plan. Requests are email only, with no SMS.
Sandbox or production
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.
Step 2 of 5
Request production access
From the Account dashboard, open the Get set up page and request production access. Describe your mail honestly and add your website.
Step 3 of 5
Create SMTP credentials
On the SMTP settings page, choose Create SMTP credentials, name the IAM user for StoryProof, and save the credentials straight away.
Step 4 of 5
Connect SES in StoryProof
In your StoryProof settings, choose SMTP and enter the endpoint, port, SMTP user name and SMTP password from the same Region.
Step 5 of 5
Test with an unverified address
Send a request to an address that is not an SES identity. If it arrives, the sandbox is behind you.
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
- Creating and verifying identities in Amazon SES, Amazon SES Developer Guide. Checked 2026-11-17.
- Request production access (moving out of the Amazon SES sandbox), Amazon SES Developer Guide. Checked 2026-11-17.
- Obtaining Amazon SES SMTP credentials, Amazon SES Developer Guide. Checked 2026-11-17.
- Connecting to an Amazon SES SMTP endpoint, Amazon SES Developer Guide. Checked 2026-11-17.
Last updated 2026-11-17.