Amazon SES Adds Six Regions: Check the Sending Interface Before Switching
On November 6, 2026, AWS said Amazon Simple Email Service (Amazon SES) is expanding to six additional Regions: New Zealand, Melbourne, Taipei, Thailand, Mexico (Central), and Spain. For teams that send order confirmations, password resets, or account alerts, the important question is not only whether a Region exists, but which SES interface it supports and how it fits your current sending setup.
That distinction matters because AWS’s General Reference separates SES into different endpoint tables for HTTPS/API, SMTP, and receiving. Regional availability by itself does not prove that SMTP sending or inbound mail handling is supported in the same way, or at the same time. Before changing production traffic, check the interface and endpoint you actually use, rather than assuming all SES features are identical across every newly announced Region.
What the AWS tables show
A concrete example is useful here. In the current AWS reference tables, ap-southeast-6 for New Zealand and mx-central-1 for Mexico Central appear in the HTTPS/API endpoint list reviewed, but not in the SMTP table reviewed. That means you should verify the exact interface you plan to use instead of relying on the Region announcement alone.
This is also why it helps to distinguish AWS acceptance from delivery. A message can be accepted by an SES API or SMTP endpoint, but successful acceptance is not the same thing as inbox placement. Likewise, sending is not the same as receiving: SES outbound mail and SES inbound mail use different endpoint and configuration considerations.
Safer checks before redirecting production mail
- Confirm the correct SES interface and endpoint for the Region you want to use.
- Verify the sender identity and DKIM status for the domain or address you will send from.
- Check whether the target Region is in sandbox or production access, and review the applicable quotas.
- Send a limited test to a mailbox you control, then confirm receipt, authentication results, and feedback monitoring.
- Keep the existing route available so you can roll back quickly if the new path does not behave as expected.
If you use SMTP and the target Region supports it, remember that SMTP credentials are Region-specific. Use the correct credentials for the selected Region and avoid copying settings from a different Region. Do not assume a newly announced Region has the same feature set as the one you already use.
For teams maintaining transactional mail, the practical takeaway is simple: treat the Region announcement as a prompt to verify, not a green light to switch blindly. Confirm the endpoint table, sending method, identity configuration, and access state first, then test carefully before moving traffic.
Primary sources
AWS What’s New: Amazon Simple Email Service adds new AWS Regions
AWS General Reference: Amazon SES endpoints and interfaces
Amazon SES developer guide: AWS Regions for Amazon SES
