Congratulations! 🎉 You made it!
This is a quick summary of what we accomplished:
All backend resources were created with Amplify and published to AWS. Additional adjustments were made by updating infrastructure templates or directly in AWS Console.
Each Lab describes just basic usage of each service. Now you can explore other features of these services. Depending on your use case, you may also consider additional directions to improve architecture further.
Amazon Pinpoint retains data for 90 days. To keep this data for an indefinite period of time or to analyze it with custom queries and tools, you can configure Amazon Pinpoint to send event data to Amazon Kinesis.
Digital User Engagement Events Database - is a reference implementation that automatically provisions and configures the AWS services necessary to start analyzing the real-time stream of engagement data from Amazon SES and Amazon Pinpoint. It deploys an AWS CloudFormation template that configures an Amazon Pinpoint event stream and an Amazon Simple Email Service configuration set to store event data in Amazon Simple Storage Service (Amazon S3). The Amazon S3 data schema is stored in an AWS Glue Data Catalog enabling data queries with Amazon Athena.
Amazon Kinesis Data Analytics - provides built-in functions to filter, aggregate, and transform streaming data for advanced analytics. It processes streaming data with sub-second latencies, enabling you to analyze and respond to incoming data and events in real time.
Data sent to Personalize is stored for internal use by the service and cannot be exported for further analysis. To avoid this issue, you can use Kinesis as a source of events for Analytics and Amazon Personalize.
If you are not planning to use created resources right after the workshop, make sure that you properly deleted them, as described in Cleanup.