Skip to main content

Guidance for Buy Online Pickup in Store/Curbside on AWS

Overview

This Guidance helps shoppers save time during their shopping experience by having their orders ready for pickup in a secure locker. Shoppers simply purchase their desired item(s) through an online channel, wait a short time for the order to be fulfilled, then receive a notification once the order is ready for pickup in a locker. Lockers are accessible through a one-time use passcode. Shoppers will no longer have to wait in line to get their items and can shop on their own schedule. 

How it works

These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.

Well-Architected Pillars

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.

This Guidance gives you near real-time visibility into access, errors, and logs, so you can respond to incidents and events before they become issues to the architecture’s functionality.

Read the Operational Excellence whitepaper 

Resources have tightly scoped AWS Identity and Access Management (IAM) roles attached to them which permits only the required services to communicate with each other. Additionally, data at rest stored in DynamoDB is encrypted with AWS Key Management Service (AWS KMS). Data in transit is encrypted with transport layer security (TLS).  

Read the Security whitepaper 

Amazon CloudWatch automatically collects logs and metrics, which you can use to create custom alerts about service performance. DynamoDB backup and restore handles data backup and recovery. You can configure these backups to be either on demand or point-in-time continuous backups.

Read the Reliability whitepaper 

This Guidance is flexible, allowing you to customize your implementation. For example, some lockers may not support message queuing telemetry transport (MQQT), but AWS IoT Core allows communication over alternate protocols.

Read the Performance Efficiency whitepaper 

All components in this Guidance, such as Lambda functions, DynamoDB, EventBridge, and API Gateway, are serverless and have built-in autoscaling. This helps you save on costs because there are no servers for you to manage, and you will only pay for the exact resources you use.

Read the Cost Optimization whitepaper 

The managed services and services with built-in autoscaling handle resources efficiently. These services scale to match demand to allow for minimum resource consumption. 

Read the Sustainability whitepaper 

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.