Amazon SES now supports tenant-level suppression lists

Published
June 1, 2026
https://aws.amazon.com/about-aws/whats-new/2026/06/amazon-ses-tenant-level-suppression-lists/

Amazon SES Tenant-Level Suppression Lists

Amazon Simple Email Service (Amazon SES) now supports tenant-level suppression lists, allowing email senders to isolate bounces and complaints per tenant. Previously, all tenants in an account shared a single suppression list, meaning one tenant's email issues caused emails for other tenants to be suppressed. With this feature, each tenant maintains a separate suppression list, ensuring that bounces and complaints affect only the tenant that generated them.

This capability benefits any sender managing distinct email streams from a single SES account. Key use cases include SaaS providers sending on behalf of multiple customers, enterprises separating transactional and marketing mail across business units, agencies managing campaigns for different brands, or any application where a complaint from one sending program shouldn't suppress delivery for another.

What to do

  • Configure suppression behavior using two settings: suppression scope (TENANT or ACCOUNT) and suppressed reasons (BOUNCE, COMPLAINT, or both).
  • Amazon SES automatically records bounces and complaints to the appropriate tenant's list.
  • Manually manage suppressed addresses using API operations including PutSuppressedDestination, GetSuppressedDestination, DeleteSuppressedDestination, and ListSuppressedDestinations with the TenantName parameter.

To learn more about tenant-level suppression lists in Amazon SES, visit the Amazon SES console or refer to the documentation.




If you need further guidance on AWS, our experts are available at AWS@westloop.io. You may also reach us by submitting the Contact Us form.

Follow our blog

Get the latest insights and advice on AWS services from our experts.

By clicking Sign Up you're confirming that you agree with our Terms and Conditions.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.