What it actually controls
A configuration set names event destinations (SNS, EventBridge, Kinesis Data Firehose, or CloudWatch), can enable reputation tracking and an automatic sending-pause option if that reputation degrades past a threshold you configure, and can assign a specific dedicated IP pool. It's applied either explicitly on a per-send basis or implicitly through an identity-level default, so a send might be using one without the caller having named it directly.
It's a regional resource, and that trips people up constantly
A configuration set created in `us-east-1` simply does not exist in `eu-west-1`, even with an identical name — SES resources of this kind are per-region, so a deploy or a send pointed at the wrong region will fail to find a configuration set that genuinely exists, just not where the request is looking. This is the single most common cause behind `ConfigurationSetDoesNotExistException`, documented in depth on its own error page.
It can pause independently of the whole account
A configuration set with reputation-based auto-pause enabled can stop sending for just the traffic routed through it while the rest of the account keeps sending normally — a materially different, more survivable failure mode than an account-wide pause, and the reason `/ses/errors/configuration-set-sending-paused` exists as a separate page from the account-level pause error, with different diagnosis and different remediation.
Separating traffic types by configuration set is the main defensive use
Routing transactional and marketing mail through separate configuration sets — potentially with separate dedicated IP pools too — means a reputation problem in one traffic type doesn't automatically pause the other. This is the same underlying idea as separating dedicated IPs by traffic type, applied at the policy layer rather than the network layer.
Why it matters
The configuration set is the piece of SES infrastructure most likely to silently diverge from what a deploy or a send actually expects — hand-created in the console once and then never reconciled with what the application code references — which is exactly the drift Wraps' own IaC deploys the configuration set alongside the code that uses it specifically to prevent.
How to check it
aws sesv2 list-configuration-sets --region us-east-1Common questions
Why does SES say my configuration set doesn't exist when I can see it in the console?
Check the region. Configuration sets are per-region resources, so a configuration set visible in the console for one region genuinely does not exist in another, even under the identical name — this is the most common cause of this exact error.
Can a configuration set pause without pausing my whole SES account?
Yes. A configuration set with reputation-based auto-pause enabled can stop only the traffic routed through it, leaving the rest of the account's sending unaffected — a different and more survivable failure than an account-wide pause.
Do I have to name a configuration set explicitly on every send?
No. An identity can carry a default configuration set that applies implicitly to sends that don't name one explicitly, which is worth checking if a send is behaving as though a configuration set were involved that nobody specified directly.