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.
You can 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. You can also 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.
Categories: general:products/amazon-ses,general:products/aws-govcloud-us,marketing:marchitecture/messaging,marketing:marchitecture/front-end-web-mobile,marketing:marchitecture/business-productivity
Source: Amazon Web Services
Latest Posts
- Durable Objects, Workers – New Asia-Pacific location hints: apac-ne and apac-se

- Durable Objects – Outbound connections keep Durable Objects alive

- (Updated) Upcoming change: Microsoft 365 Apps SAEC and MEC will unify [MC1274325]
![(Updated) Upcoming change: Microsoft 365 Apps SAEC and MEC will unify [MC1274325] 4 pexels mccutcheon 1148998](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- Dynamics 365 Customer Service – Policy strictness control for governance rules [MC1397526]
![Dynamics 365 Customer Service - Policy strictness control for governance rules [MC1397526] 5 pexels pixabay 534174](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)



![(Updated) Upcoming change: Microsoft 365 Apps SAEC and MEC will unify [MC1274325] 4 pexels mccutcheon 1148998](https://mwpro.co.uk/wp-content/uploads/2025/06/pexels-mccutcheon-1148998-150x150.webp)
![Dynamics 365 Customer Service - Policy strictness control for governance rules [MC1397526] 5 pexels pixabay 534174](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-pixabay-534174-150x150.webp)
