Implement Tenants in your Amazon SES environment, Part 2: Assessment and planning

This article explains how to plan and assess migration to Amazon SES tenants, which isolate email reputation by customer, business unit, or workload within a single AWS account.

• Tenant-based reputation isolation prevents one sender's issues from affecting others' deliverability
• Recommended approach: create one tenant per customer or business unit for complete isolation
• Pre-migration requires inventorying existing sending identities and configuration sets
• Three resource sharing strategies: complete isolation, tiered sharing, or extensive sharing
• Default limit supports 10,000 tenants per account; account-level quotas remain unchanged
• Low-friction adoption allows gradual rollout starting with subset of customers
• Senders add tenant ID via new API call or SMTP header after configuration

Amazon SES tenants enable granular reputation management for ISVs, enterprises, and organizations with multiple email streams, with phased implementation minimizing disruption.