🌴Amazon SES production access
Unlike other vendors, you can't just sign up and start sending.
First, you have to create an account and complete your integration by verifying a domain and connecting it to your EmailDelivery.com ESP platform; then you're placed into "the sandbox."
To test your Amazon SES integration while in the sandbox, you have to add and verify each of your personal email addresses one at a time, and that becomes your contact list.
To get out of the sandbox and send mail to your real contact list, you need to request production access.
If approved to get out of the sandbox, your sending limit will start out at 50,000 messages per day, and you can have the cap lifted once you've established yourself as a reasonable sender.
Amazon will initially throttle your production sending to 14 messages per second, which will automatically increase over time.
We have customers who Amazon allows to send hundreds of messages per second.
The first thing that Amazon SES is screening for is that many applicants who apply for new email marketing accounts are liars.
Fake sites, fake blogs, fake products, fake companies.
When the Trust & Safety team evaluates your site and your production access application, this is what they're looking at:
Does this site, service, or product seem real, professional, and reputable?
Is there a footer on the site with a privacy policy?
Would this site, service, or product need Amazon SES? Is there a plausible legitimate use case here?
How will this applicant build their contact list and where did their existing contacts come from?
If all of the above adds up, will this entity be sending emails that people want to read and that don't upset the reader?
And finally:
Is this otherwise legitimate applicant a competent sender? What are their hygiene practices?
How will they manage bounces, unsubs, and complaints, ensuring they will help maintain or improve Amazon's sender reputation instead of harm it?
I've spoken to Amazon about what the trust and safety team wants to see to be reassured a sender knows what they're doing, and isn't going to wildly spam and blow their account up out of negligence.
Here's their answer...
Through an integration with the EmailDelivery.com ESP platform. ✅
EmailDelivery.com has a one-click unsubscribe in the footer and a one-click list-unsubscribe header is attached as a backup in case the integrated email delivery service doesn't include its own ✅
The EmailDelivery.com ESP platform integration uses Amazon SNS and event publishing. ✅
Real-time reputation metrics are shown prominently in the EmailDelivery.com platform UI reporting as webhooks come back in live from Amazon. ✅
Bounces, unsubs, and complaints are suppressed account-wide automatically the first time they're seen. ✅
We will also be using the reputation metrics dashboard in the Amazon SES console as a sanity check and backup to monitor our bounce and complaint rates and verify the information we're seeing in the EmailDelivery.com platform is accurate on an ongoing basis. ✅
The idea would be to include as much specific details on the SES features they will be leveraging so that the AWS Trust and Safety Team are assured that they are aware and will implement best practices
You'll be asked by Amazon SES to non-specifically state your "Use case".
Just answer general questions like these as comprehensively as possible:
What does your site do?
How do you plan to build or acquire your mailing list?
What will you use Amazon SES for?
If you're switching from another ESP, attach recent invoices proving you're a valid sender with a regular business relationship with another service.
Provide links to social media accounts associated with your verified domain that have a following and organic engagement.
Attach examples of emails you plan on sending - these better be good and show an unsubscribe footer with a full name and address for the sender and "you have received this email because you...." memo.
Bottom line:
Just don't look like a spammer. 👍
Last updated
Was this helpful?