Pinpoint Migration Documentation#8585
Open
ekjotmultani wants to merge 17 commits into
Open
Conversation
… and push notification pages
…sing sections
- Fix Lambda event format to use event['Items']['CustomerProfiles'] per
AWS docs (was incorrectly using event.get('CustomerProfiles', []))
- Fix Lambda registration: use Connect console Outbound campaigns UI,
not associate-lambda-function (which is for contact flows)
- Add End User Messaging App ID explanation
- Add IAM permissions for Lambda execution role
- Add prerequisites section (Connect instance, Customer Profiles)
- Add analytics-only migration path (Kinesis Data Streams)
- Add identifyUser migration guidance with field mapping
- Move notification content to environment variables
- Remove duplicate callouts and redundant explanations
- Fix boto3 client comment
- Wrap IAM policy and Lambda code in Accordion (collapsible) - Add BlockSwitcher with Kotlin/Swift/Dart tabs for device registration - Wrap put-profile-object-type CLI in Accordion - Add summary text outside accordions so readers get context without expanding
…nt-migration-doc # Conflicts: # src/pages/[platform]/start/platform-setup/index.mdx
jvh-aws
reviewed
Jun 1, 2026
| ```python | ||
| import boto3 | ||
|
|
||
| eum = boto3.client('pinpoint', region_name='us-east-1') |
Contributor
There was a problem hiding this comment.
wouldn't a TS example make more sense?
harsh62
previously approved these changes
Jun 1, 2026
- Add platform to getStaticProps props (required by docs framework) - Add page to directory.mjs for sidebar rendering - Add headingLevel/eyebrow to Accordion components per style guide - Add cspell words: customerprofiles, fileb, rebranded
jvh-aws
reviewed
Jun 1, 2026
| ## If you only use Amplify Analytics | ||
|
|
||
| If you only use Amplify Analytics (`recordEvent`, session tracking) and don't use push notifications, your migration path is **Amazon Kinesis Data Streams** — not Connect. See [Set up Kinesis Data Streams](/[platform]/build-a-backend/add-aws-services/analytics/streaming-analytics/) for setup instructions. The Amplify Kinesis client is already available. | ||
|
|
Contributor
There was a problem hiding this comment.
Can we improve the wording / tone here (as discussed)?
Addresses review feedback — Amplify backend is TypeScript-first. Converts: direct send, endpoint import, Lambda, identifyUser, and Flutter backend proxy from Python to TypeScript.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of changes:
dds a new doc page guiding customers through migrating Pinpoint push notification campaigns before the Oct 2026 EOL. Covers two paths:
Direct send — call End User Messaging directly (no Connect needed)
Connect Journeys — full campaign UI with segmentation via Customer Profiles + a Custom Action Lambda for push delivery
Includes: prerequisites, IAM policies, Lambda implementation with correct outbound campaign event format, device registration code (Kotlin/Swift/Dart), identifyUser field mapping, and an analytics-only callout pointing to Kinesis.
Related GitHub issue #, if available:
#8603
Instructions
If this PR should not be merged upon approval for any reason, please submit as a DRAFT
Which product(s) are affected by this PR (if applicable)?
Which platform(s) are affected by this PR (if applicable)?
Please add the product(s)/platform(s) affected to the PR title
Checks
Does this PR conform to the styleguide?
Does this PR include filetypes other than markdown or images? Please add or update unit tests accordingly.
Are any files being deleted with this PR? If so, have the needed redirects been created?
Are all links in MDX files using the MDX link syntax rather than HTML link syntax?
ref: MDX:
[link](https://docs.amplify.aws/)HTML:
<a href="https://docs.amplify.aws/">link</a>When this PR is ready to merge, please check the box below
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.