This Guidance helps you set up a loyalty reward redemption lifecycle for your customers that includes catalog, orders, custom payment methods, initiative launches, and fulfillment. Loyalty reward redemption improves customer satisfaction and re-share behaviors while increasing revenue. However, building a loyalty program can be complex and costly, as these programs require in-depth expertise of inventory selection, purchasing negotiation, and customer portal management. 

This Guidance uses AWS services and Amazon Business to enable the redemption and fulfillment of the loyalty program, leveraging the Amazon Prime Delivery experience. Loyalty customers will have access to a customized member portal and SMS notifications about shipment confirmation and delivery, while you will have access to a data lake that consolidates customer order information and preferences. 

Please note: [Disclaimer]

Architecture Diagram

Download the architecture diagram PDF 
  • Loyalty User Experience

  • This architecture diagram shows how loyalty users can access the portal as defined by the catalog manager to redeem products using points and money. Amazon Business then delivers these products directly to users.

  • Catalog Manager and Business Operator Experience

  • This architecture diagram shows how the catalog manager configures the experience and appearance of the loyalty portal and how the business operator monitors loyalty program performance. 

Well-Architected Pillars

The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

  • Amazon CloudWatch stores all logs and metrics from all the services used in this architecture. CloudWatch can also ingest information from customer code running in Amazon ECS. This Guidance is designed to provide the information necessary to understand its internal state (for example, metrics, logs, events, and traces) across all components for observability. It also captures changes in state, user activity, and access privileges to monitor the health of the workload, identify when outcomes are at risk, and enable effective responses.

    Read the Operational Excellence whitepaper 

  • AWS Identity and Access Management (IAM) policies control services interactions. Policies and roles are granted the least amount of permissions required for the application to operate. IAM policies and roles limit unauthorized access to services so that a malicious actor, misconfiguration, or bug cannot expose user data or impact application operations. AWS WAF blocks malicious actors from accessing the authentication layer hosted on Amazon Cognito. It protects the web application from a known list of offending IP addresses. AWS Key Management Service (AWS KMS) keys encrypt Aurora and Amazon Redshift data in transit using TLS 1.2 or higher so that malicious actors cannot read confidential information.

    Read the Security whitepaper 

  • AWS Amplify allows a modern application (integrated into a development pipeline) to work reliably and at scale because it embeds a content delivery network (CDN). This Guidance describes an application that may be accessed simultaneously by thousands of users. In case of load spikes or technical issues on edge nodes or the origin, Amplify redirects traffic, scales its capacity, and caches original content, allowing the application to serve traffic steadily at all hours of the day. While Amplify reliably serves static content, API Gateway serves dynamic content to users, using caching and throttling to not overwhelm the backend.

    Additionally, Aurora replicates data across different Availability Zones and supports automated failover for minimal service interruption. Aurora also provides automated backups that you can use to restore application functionality in case of human errors or malfunctions.

    Read the Reliability whitepaper 

  • Aurora delivers significant PostgreSQL performance by tightly integrating the database engine with an SSD-based virtualized storage layer purpose-built for database workloads, reducing writes to the storage system, minimizing lock contention, and eliminating delays created by the database process thread. Aurora features a storage system that delivers high performance, availability, and performance, and this storage can be increased for up to 15 low-latency read replicas.

    Additionally, Amplify CDN can improve performance for remote users by distributing and caching requests. API Gateway scales automatically to support traffic spikes and can cache requests to accelerate the requests and reduce load on the database. 

    Read the Performance Efficiency whitepaper 

  • There are no minimum fees or upfront commitments for using Amplify, API Gateway, Step Functions, or Amazon ECS. Amazon ECS can run containers without having to provision or manage Amazon Elastic Compute Cloud (Amazon EC2) instances. Amazon ECS supports auto scaling and can also use Amazon EC2 Spot Instances to achieve a significant cost reduction without sacrificing performance. Aurora offers an I/O optmized configuration that can be useful if the database is under a sustained heavy I/O load, as it offers zero charges for read and write I/O operations.

    Read the Cost Optimization whitepaper 

  • Amazon ECS allows customer to fine tune container requirements, avoiding provisioning for peak times. Amazon ECS and Aurora also support AWS Graviton processors for the underlying clusters. AWS Graviton processors offer the best price performance per watt of energy, and latest generations of AWS Graviton processors use up to 60% less energy for the same performance. 

    Read the Sustainability whitepaper 

Implementation Resources

A detailed guide is provided to experiment and use within your AWS account. Each stage of building the Guidance, including deployment, usage, and cleanup, is examined to prepare it for deployment.

The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.

Open implementation guide
Open sample code on GitHub

Related Content

[Subject]
[Content Type]

[Title]

[Subtitle]
This [blog post/e-book/Guidance/sample code] demonstrates how [insert short description].

Disclaimer

The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.

References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.

Was this page helpful?

 Feedback