How the platform connects to SES
Amazon SES (Simple Email Service) is the email sending service in the AWS cloud. In Endora Commerce it is one of three providers on the email adapter list, next to SMTP and SendGrid. In the admin panel, under credentials, you create a configuration of the “email adapter” type, pick Amazon SES as the provider and enter three values: the region, the access key ID and the secret access key. The secret key is encrypted at rest and is never returned in plain form once saved.
Moving to SES from your own SMTP server or from SendGrid means pointing at a different configuration, with no change to the code of the modules that send messages.
What to prepare on the AWS side
- A verified sender identity. SES requires you to verify every domain or address you use in the From field. In practice that means adding DNS records for the shop’s domain.
- Leaving the sandbox. Every new SES account starts in sandbox mode, separately in each region. In that mode you can only send to verified addresses and within a small daily limit, so before the shop goes live you need to file a production access request. AWS asks about the type of mail (transactional or marketing) and your website address.
- An IAM access key. The platform authenticates with an AWS access key, so it is worth creating a dedicated IAM user for it, with permissions limited to sending through SES, and entering in the configuration the same region in which the domain was verified.
SES counts sending limits per region and by number of recipients, not messages.
Which messages go this way
All the mail the platform sends in response to events passes through the transactional transport:
- orders: order confirmation, order comment, reorder, order created by an administrator,
- payments and shipping: payment status change, shipment created,
- returns: return authorized or rejected,
- company accounts: email verification, organization invitation, new registration,
- inventory: low stock and back in stock.
An administrator edits the subject, content and look of each of these messages in the admin panel, globally or separately per sales channel and language, with a preview on sample data. An individual message can also be switched off, except for those needed to create an account. SES receives a finished HTML message with a plain-text alternative; no templates are used on the AWS side.
What the platform knows and what SES knows
| Question | Where the answer is |
|---|---|
| Was the message handed over for sending? | The delivery record in the platform database: sent, suppressed or failed, with the recipient, message type, channel and time of the attempt |
| Did it reach the inbox, or come back as a bounce or a complaint? | Amazon SES: bounce and complaint notifications and account statistics |
A “sent” status means SES accepted the message, not that the recipient received it. The sending itself runs in the background, through a queue backed by Redis, so it does not hold up order processing. Leaving the sandbox and having correct credentials are still worth checking before the shop launches, not after the first order.
Newsletter on SES: separate credentials
The newsletter module has its own sending provider, independent of the transactional transport and set in the admin panel, with the secret stored encrypted. That provider can be SES too, on a separate access key.
Campaigns go out through a separate queue, with a configurable limit of messages per second. This lets you match the sending pace to the limit granted to your SES account, and a large campaign does not delay order confirmations. If you run your newsletter in an external mailing platform, the whole module can be switched off without affecting transactional mail.
When to choose SES
SES is the natural choice when the company already has an AWS account, for example it keeps the shop’s files in Amazon S3, and wants its mail in the same place, in a region of its choice, including a European one. It does, however, need someone comfortable with IAM, DNS records and the production access request. If there is no such person, it is simpler to start with SendGrid or with an SMTP server the company already uses. Because all three options are picked from the same provider list, the decision can be changed later without rebuilding the shop.