Self-hosting
SES tenancy
Understand how teams map to AWS SES tenants.
One team, regional tenants
Creating a team queues its tenant in the default region. Adding a domain in another enabled region provisions a tenant there. Domain identities and configuration sets are associated with that team’s tenant.
Sending isolation
Every send carries TenantName and ConfigurationSetName derived from the verified domain. There is no untagged account-level fallback. Tenant suppression lists isolate bounce and complaint handling. AWS billing, account quotas, and sandbox state remain shared.
Pause and recover
Installation administrators can pause or resume regional tenants under Team sending. Queued mail fails when claimed while paused; scheduled mail is checked when due. Resuming permits new sends and does not replay failed messages. AWS restrictions still apply.
{"failed":{"reason":"Tenant sending is unavailable"}}Remove resources
Remove domains before deleting a team. Cleanup checks ownership and remaining associations. Failed tenant removal stays visible for the installation administrator to retry.
The operator’s failed tenant-cleanup list is paginated. Use its page controls to find outstanding tenants and retry cleanup; the first page is not the complete queue.