Amazon Pinpoint ends October 30, 2026. Your email moves to Amazon SES.

AWS is not deprecating a feature — it is turning off the console. After October 30, 2026 you lose access to your endpoints, segments, campaigns, journeys, and analytics. AWS's own recommendation for Pinpoint email is Amazon SES.

The delivery half of that migration is straightforward. The half nobody warns you about is that SES has no contacts, no segments, no campaigns, and no journeys — and AWS's answer for those is a contact-center product. This page covers both halves.

What actually goes away

Pinpoint was two products sharing a console: an engagement layer and a set of channel APIs. Only one of them is ending. Sorting your usage into these three buckets is the first useful thing you can do.

Source: Amazon Pinpoint end of support (AWS documentation).

AWS's recommended path splits your email stack across three services

Read the guide carefully and the recommendation is: SES for delivery, Amazon Connect for segments and campaigns and journeys, Kinesis for events. That is coherent if you run agent-assisted outbound with predictive dialing. If Pinpoint was how you sent onboarding email, you are being asked to adopt a contact center to replace a drip sequence.

In both columns the mail leaves your own AWS account through your own SES identities. Wraps changes what sits around SES, not who owns it.

Where Wraps fits — and where it doesn't

If Pinpoint was your push and in-app channel, this page only solves part of your problem. Those APIs are unaffected by the shutdown, so the honest answer is to leave them where they are and migrate the email half.

The migration, in order

The ordering matters more than the effort. Two steps have external clocks on them — the analytics export window and SES production access — and both are cheap to start today.

1. 1

   Export everything, this week

   Analytics KPIs are only available for the trailing three months, so this is the one item with a decaying window. Create a segment with no filters and export it to S3 to capture every endpoint, then pull your definitions with get-segment, get-campaign, get-journey, and list-templates. Do this before you decide anything else.

2. 2

   Separate the email workload from the rest

   SMS, push, WhatsApp, voice, and OTP are already on AWS End User Messaging and need no migration at all. Confirm that, and the problem shrinks to email plus whatever engagement logic sat on top of it.

3. 3

   Stand up SES with its supporting stack

   npx @wraps.dev/cli email init provisions SES, EventBridge, Lambda, DynamoDB, SQS, and scoped IAM roles into your AWS account in about two minutes. Every resource is namespaced wraps-email-, so if you already have SES identities configured, use wraps email connect instead and nothing existing is touched.

4. 4

   Get out of the SES sandbox early

   A new SES account starts in the sandbox and can only send to verified addresses. Production access is a support request that can take days and is routinely denied on the first try. Start it the day you stand up SES, not the week you cut over. Our production access guide covers what the request needs to say.

5. 5

   Port templates

   Pinpoint and SES both render Handlebars, so the markup carries over. What changes is the placeholder namespace — a Pinpoint template referencing {{User.UserAttributes.Plan}} has to be rewritten against whatever attribute shape you land on. If you would rather stop hand-editing HTML entirely, Wraps templates are React Email components that live in your repo and get reviewed in pull requests.

6. 6

   Rebuild segments, campaigns, and journeys

   This is the part AWS routes through Amazon Connect. If you are not running a contact center, Wraps covers the same ground as contacts, segments, broadcasts, and workflows — sending through the SES account you just stood up, on your own domains and your own reputation.

7. 7

   Cut over and verify

   Run both paths in parallel for a sending cycle, compare delivery and bounce rates, then retire the Pinpoint application. Give yourself weeks of margin: after October 30, 2026 there is no console to go back to.

What it costs after the move

Pinpoint billed email at the SES rate, so delivery cost is roughly a wash — with one change worth knowing about. Since July 2026 SES has pricing plans, and new accounts are defaulted to Essentials at $0.16 per 1,000 emails rather than à la carte at $0.10 per 1,000. An account defaulted into Essentials can move back to à la carte with immediate effect.

If you are standing up a fresh SES account for this migration, you are standing up a defaulted one. wraps email plan reads which plan each Region is on, models your real volume against all four, and switches you back if à la carte is cheaper.

Frequently asked questions