AWS will end support for Amazon Pinpoint on October 30, 2026. Learn what's going away and what's surviving, what your migration options are, and how to quickly audit your environment to see your exposure.
If your application relies on Amazon Pinpoint, you likely already know that AWS is retiring a chunk of the service on October 30, 2026.
As the cutoff date approaches, we are actively helping our customers' engineering and marketing teams untangle their Amazon Pinpoint workloads. AWS is not shutting down the service completely, but they are initiating a drastic architectural shift. Moving forward, they are transitioning away from the Pinpoint API namespace and consolidating the raw messaging infrastructure under Amazon End User Messaging. In doing so, AWS is officially deprecating the marketing UI and all marketing-specific features, meaning workflows dependent on those capabilities will break if not migrated.
In this blog, we will break down what is actually happening, what your options are, and how to quickly audit your environment to see your exposure.
AWS is stripping out Amazon Pinpoint's marketing automation and orchestration layer. If you have non-technical users logging into the AWS console to manage audiences or build drip campaigns, that workflow is dead come October.
Specifically, you will lose access to:
For an organization, the upcoming deprecation of Amazon Pinpoint's marketing layer isn't just about swapping out an API endpoint, it is a looming operational bottleneck. Right now, Pinpoint provides a visual orchestration UI that allows your marketing and product teams to autonomously build multi-step customer journeys, manage dynamic audience segments, and schedule campaigns without writing code. When AWS shuts this interface down in October, that autonomy disappears. If these workflows aren't migrated to a third-party customer engagement platform soon, the burden of executing every targeted campaign, querying audience lists, and hard-coding drip logic will fall directly onto your engineering team. Losing this layer doesn't just break your marketing stack; it threatens to turn your developers into an ad-hoc marketing execution arm just to keep revenue-driving communications afloat.
If you strictly use Amazon Pinpoint as a dumb pipe, meaning your own backend handles the logic and just calls the Amazon Pinpoint API to fire off a transactional text or push notification, you are mostly in the clear.
AWS has repackaged the underlying channels into a developer-focused suite called AWS End User Messaging. The following capabilities aren't going anywhere:
For email, AWS is directing customers to consolidate everything under Amazon Simple Email Service (SES).
Because AWS isn't offering a direct, native replacement for the Amazon Pinpoint marketing UI, your migration path depends entirely on how you use the service today. These changes are not optional or something you can do later when it's convenient for the team; these are changes you must do before the October cutoff date.
The hardest part of this migration is often just figuring out who in your organization is actually using these deprecated features. Rather than spending weeks digging through CloudTrail logs and codebases, we built a shortcut.
Caylent has developed and open-sourced an Amazon Pinpoint Deprecation Assessment Tool.
You can run this lightweight script against your AWS environment, and it will output a clear report detailing exactly how deeply entrenched you are. It flags active Journeys, counts your endpoints, and maps out your channel usage so you know exactly what needs to be migrated.
Here is a step-by-step guide to installing, configuring, and running the assessment tool in your AWS environment.
Before you begin, ensure you have:
The tool is strictly read-only; it will never create, modify, or delete any AWS resources. However, it does require permission to read your Pinpoint configurations.
You will need an IAM role or user with the necessary read-only permissions. The Caylent repository provides a pre-built IAM policy (iam-policy.json) containing the exact actions needed.
Key permissions include:
(Note: Because Pinpoint doesn't support resource-level constraints for most read operations, the policy requires Resource: "*").
The fastest way to install the tool is using uv (Astral's fast Python package installer), but standard pip works perfectly fine as well.
Run one of the following commands in your terminal:
Using uv (Recommended):
Bash
Brian Tarboxuv tool install pinpoint-eda
Using pip:
Bash
pip install pinpoint-eda
The tool is designed to be highly flexible, whether you want a guided experience or need to execute it programmatically via CLI flags.
If you just type the tool's name, it launches an interactive wizard. This wizard automatically discovers your local AWS profiles from ~/.aws/ and guides you through the scan.
Bash
pinpoint-eda
? How do you want to authenticate? AWS profile (from ~/.aws/config)
? Select AWS profile(s) to scan (space to select, enter to confirm): done
? AWS profile name: xxxxxxx
? Add another profile? No
? Region selection: Auto-discover (probe all regions for Pinpoint apps)
? Scanner selection: Run all scanners (recommended)
? Max parallel threads: 5
? Output directory: ./pinpoint-eda-output
? JSON-only output (no Rich display)? No
Scan Configuration Summary:
Accounts: xxxxxx
Regions: auto-discover
Scanners: all
Max workers: 5
Output: pinpoint-eda-output
? Start scan with these settings? Yes
Amazon Pinpoint End of Support: October 30, 2026 240 days remaining
Overall Migration Complexity: LOW
Option B: Command Line Option
# Direct scan with a profile
pinpoint-eda scan --profile my-profile
# Specific region (skip auto-discovery)
pinpoint-eda scan --profile my-profile --region us-east-1
# Multi-account
pinpoint-eda scan --profile prod --profile staging
# Dry run -- discover apps without scanning
pinpoint-eda scan --profile my-profile --dry-run
# Re-render or export a previous report
pinpoint-eda report ./pinpoint-eda-output/pinpoint-eda-report.json
pinpoint-eda export ./pinpoint-eda-output/pinpoint-eda-report.json
With October fast approaching, the window for planning is closing. Run our assessment tool to get a baseline of your environment. If your report reveals significant dependencies on depreciated features, our team can help you design and execute a seamless transition to Amazon End User Messaging, Amazon Connect, and/or a third-party CEP, so you stay ahead of the deadline with confidence.
Brian is an AWS Community Hero, Alexa Champion, has ten US patents and a bunch of certifications, and ran the Boston AWS User Group for 5 years. He's also part of the New Voices mentorship program where Heros teach traditionally underrepresented engineers how to give presentations. He is a private pilot, a rescue scuba diver and got his Masters in Cognitive Psychology working with bottlenosed dolphins.
View Brian's articles
Chatbots aren’t the only way to surface AI, and often, they’re the wrong choice. Discover intelligent interface patterns that drive AI adoption, build user trust, and deliver measurable ROI without forcing users to craft the perfect prompt.
Learn why 85% of AI projects fail and how strategic UX design drives trust, adoption, and measurable ROI.
Explore all the exciting announcements from Dr. Ruba Borno's partner keynote. From the general availability of AWS Transform compatibility to new AWS Marketplace capabilities, the updates showcased powerful new ways for partners to deliver value.
