Since Notifuse 37.1, an Amazon SES integration can isolate its sending reputation. When you switch this on, Notifuse creates an SES tenant for the integration in your AWS account, with its own suppression list, and sends every message through it. One workspace's bounces and complaints then no longer count against the other workspaces that share the same AWS account.
Shared reputation
Without tenants, an AWS account has one SES reputation and one suppression list per region. AWS watches the bounce and complaint rates of the whole account and can pause its sending when they climb too high. Every workspace sending through that account is affected: a bad import in one of them can stop email for all the others, and an address that bounced for one is suppressed for the rest.
SES tenants
A tenant is a group of SES resources inside your account (here a configuration set and sender identities) that AWS tracks separately. It gets its own reputation and its own bounce and complaint metrics and, if configured that way, its own suppression list. When a tenant's rates go wrong, AWS can pause that tenant and let the rest of the account keep sending.
Ten clients
Say an agency runs ten client workspaces on one Notifuse installation, each with an SES integration using the agency's AWS keys. One client imports an old trade-show list, and a fifth of it bounces. Without tenants, the account's bounce rate rises for everyone, the nine other clients risk a pause they did nothing to deserve, and the bounced addresses are suppressed in their workspaces too. With isolation on, the bounces land on that client's tenant alone. Its reputation drops and its suppression list grows, while the nine others keep sending under their own.
What Notifuse creates
When you save an SES integration with Tenant isolation on, in its Reputation panel, Notifuse asks you to confirm, because AWS bills each tenant, and then sets up the following in your account:
A tenant named
notifuse-<integration ID>, whose suppression list is scoped to the tenant for bounces and complaints. A tenant created by hand shares the account's list unless configured otherwise, so if Notifuse finds one under that name, it corrects its scope.The configuration set the integration sends through,
notifuse-<integration ID>unless you named your own. Notifuse creates it if it is missing and associates it with the tenant.The sender identities. For each sender of the integration, every verified identity that covers it (the exact address, its domain or a parent domain) is associated with the tenant.
Notifuse records the tenant on the integration only once its configuration set is associated, because SES rejects a tenant send whose configuration set isn't. A half-finished setup therefore leaves sending as it was. Saving again runs the same steps, which associates a sender you added later and finishes a partial run.
Sending
Every message from an isolated integration, whether broadcast, automation or transactional, carries the tenant and the configuration set. To support this, sending moved to the SES v2 API, the one that accepts a tenant. The integration card shows the result under Reputation: "isolated" with the tenant's name, "isolation requested but not provisioned" when the switch is on but no tenant is in use yet, or "shared with the rest of this AWS account".
Webhooks
Delivery, bounce and complaint events still travel from the configuration set to Notifuse through Amazon SNS. Register webhooks, in the menu of the integration's card, can recreate the configuration set, which AWS treats as a new resource with no tenant, so Notifuse associates it again right after. While a tenant uses the configuration set, removing the webhooks leaves it in place, since sends depend on it. Exit on reply keeps working, because replies still come back through the receipt rule that Register webhooks sets up.
In AWS
The integration's AWS keys need permission to manage tenants. On top of sending and webhooks, isolation uses ses:CreateTenant, ses:GetTenant, ses:PutTenantSuppressionAttributes, ses:CreateTenantResourceAssociation and ses:ListEmailIdentities. Add ses:ListTenants and ses:ListTenantResources for the name pickers, and ses:DeleteTenant with ses:DeleteTenantResourceAssociation so that deleting the integration also removes its tenant. After saving, Notifuse names any permission it was refused, and any sender with no verified identity, whose emails would fail with or without a tenant. The tenant is created in the integration's region, next to its configuration set and identities.
Off and on
If you switch isolation off and save, the next message goes out under the account's shared reputation. The tenant stays in AWS with its suppression list and history, and switching isolation back on picks up the same tenant. It keeps being billed as long as it exists. Deleting the integration removes its configuration set and the tenant Notifuse created, in the order AWS requires, and with them that suppression list and history.
Your own tenant
The Advanced panel, under it, has two optional fields, and both suggest the names found in your account. Fill in Configuration set to send through a set you manage instead of Notifuse's; Notifuse attaches its event destination to it and never creates or deletes it. Fill in SES tenant to send through a tenant you manage, which Notifuse never deletes. That field can't be combined with the switch, and the tenant needs your configuration set associated with it, or SES rejects the sends.
Licence
Since Notifuse 40, switching isolation on in a self-hosted installation needs a licence key, Studio or above; without one, the switch is greyed out. A tenant already in use keeps sending whatever happens to the key, because sending never checks the licence. Without a key you can still switch isolation off, but not back on. An agency with ten workspaces holds a key anyway: without one, an installation creates only three.
Not yet
The console doesn't show whether AWS has paused a tenant, so check that in the SES console.
Notifuse can't yet remove a tenant on its own: a tenant switched off keeps billing until you delete the integration, or remove the tenant yourself in AWS.
A sender added through the API with
workspaces.updateIntegrationisn't associated with the tenant until the integration is next saved in the console or its webhooks are registered.
Getting started
As a workspace owner, open Settings → Integrations, edit your Amazon SES integration, switch Tenant isolation on, save and confirm the tenant. The Amazon SES documentation lists the IAM permissions and each step, and the licence page shows how to install a key.
