View a markdown version of this page

Serverless Notifications for Mobile Games with Amazon Pinpoint - Serverless Notifications for Mobile Games
Serverless Notifications with Amazon Pinpoint diagramFurther readingDiagram history

Serverless Notifications for Mobile Games with Amazon Pinpoint

Publication date: March 10, 2021 (Diagram history)

This architecture provides an alternative notification flow that uses Amazon Pinpoint for campaign-based messaging, A/B testing, and segmented audience targeting with built-in streaming analytics.

Serverless Notifications with Amazon Pinpoint diagram

Reference architecture diagram showing how to build a serverless notifications pipeline for mobile games by using Amazon Pinpoint for campaigns and segmented messaging.

The following steps describe the architecture:

  1. The game client sends notification information to an Amazon API Gateway REST endpoint. You can update the API version and scale to handle large numbers of requests automatically.

  2. To access underlying AWS services through the SDK, the mobile game client requests temporary credentials from Amazon Cognito Identity pools.

  3. The mobile game client can also use the AWS Mobile SDK to invoke Amazon Pinpoint directly with a payload. The device can register or update endpoints dynamically.

  4. API Gateway requests Amazon Pinpoint, which performs additional logic like message token translation, segmented message delivery, and streaming analytics for further analysis.

  5. Amazon Simple Notification Service uses the push notification service credentials and mobile device tokens. After receiving the message, all subscribers receive the push notification through providers like Firebase or Apple push notification service.

  6. An AWS Lambda function subscribes to DynamoDB Streams to sync users to Amazon Pinpoint.

  7. A marketing employee can initiate a campaign, personal message, or A/B testing through the AWS console for Amazon Pinpoint.

  8. Campaign and message sending data is streamed to Amazon Kinesis for streaming event analytics or to be stored for later insights in a data lake.

Further reading

For additional information, see the following resources:

Diagram history

To be notified about updates to this reference architecture diagram, subscribe to the RSS feed.

ChangeDescriptionDate

Initial publication

Reference architecture diagram first published.

March 10, 2021

Initial publication

Reference architecture diagram first published.

March 10, 2021

Note

To subscribe to RSS updates, you must have an RSS plugin enabled for the browser you are using.