- Newest
- Most votes
- Most comments
Thank you for reporting this issue. Based on the information available, this does appear to be a configuration gap in the AWS European Sovereign Cloud (EUSC) region.
When setting up a custom MAIL FROM domain in Amazon SES, the service requires you to publish an MX record pointing to a region-specific feedback endpoint. This endpoint is used by SES to receive bounce and complaint notifications from email providers. SES automatically specifies the correct feedback endpoint for each region during the custom MAIL FROM domain configuration process.
In standard AWS Regions, these feedback endpoints follow the pattern feedback-smtp.[region].amazonses.com and are documented and functional. However, the AWS European Sovereign Cloud is a new, independent cloud infrastructure that is physically and logically separate from existing AWS Regions, with all components located within the EU.
Given that the EUSC is a distinct infrastructure with its own operational model and technical controls, it's possible that either:
- The feedback endpoint infrastructure has not yet been fully deployed in this region, or
- The endpoint naming convention or DNS configuration differs from standard AWS Regions due to the sovereign cloud's use of dedicated infrastructure, including dedicated Amazon Route 53 nameservers that exclusively use European top-level domains
I recommend opening a support case with AWS to report this issue, as this appears to be either a missing infrastructure component or a documentation/configuration error that needs to be addressed for SES to function properly with custom MAIL FROM domains in the European Sovereign Cloud region.
Sources
Amazon Simple Email Service endpoints and quotas - AWS General Reference
Regions and Amazon SES - Amazon Simple Email Service
Opening the AWS European Sovereign Cloud | AWS News Blog
I do not have the support plan, so I cannot open a technical case.
Ah, the correct address is:
feedback-smtp.eusc-de-east-1.amazonses.eu
But it is still wrong on the AWS Console page
Relevant content
- asked 3 years ago

Have you tried using the Feedback link that is available on every AWS service console page?