(Notice): Pinpoint End Of Support

[ekjotmultani]

Description

AWS will end support for Amazon Pinpoint on October 30, 2026,, and is no longer accepting any new users as of May 20 (see the linked doc). The guidance is to use AWS End User Messaging for push notifications and SMS, Amazon Simple Email Service for sending emails, and Amazon Connect for campaigns, journeys, endpoints, and engagement analytics. Finally they recommend Amazon Kinesis for event collection and mobile analytics.

This assortment of services will together make up what Pinpoint has offered in the past, and this ticket is tracking interest in these services and migration from Pinpoint.

Categories

• Analytics
• API (REST)
• API (GraphQL)
• Auth
• Authenticator
• DataStore
• Notifications (Push)
• Storage

Steps to Reproduce

Please thumbs up and/ or comment on this ticket with any thoughts you have!

Screenshots

No response

Platforms

• iOS
• Android
• Web
• macOS
• Windows
• Linux

Flutter Version

3.32

Amplify Flutter Version

2.6.2

Deployment Method

Amplify CLI (Gen 1)

Schema

[github-actions]

This issue was opened by a maintainer of this repository; updates will be posted here. If you are also experiencing this issue, please comment here with any relevant information so that we're aware and can prioritize accordingly.

[jamilsaadeh97]

Hello!

We're using Pinpoint Notifications and Analytics in our apps. As I understand, the notifications capabilities won't be affected, but we're also using campaigns, segments, and endpoints. We're also using analytics events and metrics.

It would be great to know what is the plan of Amplify Flutter, if it will support the services mentioned as a replacement.
Since we rely on those services, it would be great if we have time to migrate and make sure everything is working correctly.

Thank you!

[tyllark]

Hello @jamilsaadeh97, current users can continue to use Pinpoint until October 30, 2026 without issue. The recommended replacement for Pinpoint Analytics is Amazon Kinesis, however Amplify does not have an interface for this service.

We are still researching a path forward with Amplify and will respond here when we have an update. Our intent is to give ample time to migrate and verify any changes.

[GERASM1]

Hello, I have a question. I’m only using Pinpoint to manage push notifications on mobile devices — is there anything I should be concerned about? Will I be affected by this change?

The notice says that Mobile Push won’t be impacted. Does that mean:

1. If I’m using aws-amplify/push-notifications (from Amplify version 6) to listen for incoming notifications and retrieve device tokens, can I expect it to continue working without any changes on my side? I use those device tokens to send push notifications to specific users via a Lambda function.

2. If I’m sending notifications through a Lambda function that uses the Pinpoint library from the AWS SDK for Node.js, will that continue to work as well? I created the Lambda function using the Amplify CLI, which granted the necessary permissions to access Pinpoint. I also use the ANALYTICS_NEURALIZEPINPOINT_ID environment variable (created by Amplify) to target the correct Pinpoint instance.

For example, to notify users when they receive a message:

1. I obtain the user’s device token using the aws-amplify/push-notifications library.
2. I save the device token in my database, associated with that user.
3. When another user sends a message to this user, I retrieve the target user’s device token from the database.
4. I pass the device token to my Lambda function as part of the request.
5. The Lambda function uses the AWS SDK’s Pinpoint module, together with the environment variable provided by Amplify, to send the push notification through the appropriate channel.
6. On the receiving user end I use aws-amplify/push-notifications to listen whenever a notification arrives and change states accordingly.

Is there anything I should rework from this?

Thank you for clarifying!