Combine AWS edge compute services with your on-premises retail facility to improve both the customer experience and operational efficiency. Stream and analyze camera footage, optimize your point of sale systems, deploy targeted marketing content, and capture and manage application data.

Architecture Diagram

[Architecture diagram description]

Download the architecture diagram PDF 

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.

  • The proposed architecture diagram will use edge and cloud-based services with Amazon CloudWatch alarms and logs.

    Read the Operational Excellence whitepaper 
  • The architecture diagram uses a combination of managed services that leave a large portion of responsibilities to AWS, following best practices of security including AWS Identity and Access Management (IAM) roles scoped down, encryption at rest, and services deployed at the edge within a customer location. The edge services will be deployed using best practices such as IoT Greengrass devices that authenticate using certificates, but the physical security of these will be the responsibility of the customer.

    Read the Security whitepaper 
  • The managed cloud-based services are reliable by default; redundancy is built into Amazon SageMaker and Amazon API Gateway, for example. Requirements for reliability at the edge will need to be evaluated in line with business need. Mechanisms such as caching events and messages locally can be used in the event of a connectivity outage to AWS, and a significant benefit of implementing compute at the edge is bracing the reliance on a reliable network connection.

    Read the Reliability whitepaper 
  • The cloud-based services scale to handle significant event and message volumes (such as AWS IoT Core), making use of managed services such as SageMaker Neo, which removes the need for manually scaling and monitoring performance.

    Read the Performance Efficiency whitepaper 
  • Using serverless cloud-based services helps ensure minimum cost is incurred, and the edge services included in the architecture diagram will help to reduce costs by processing data locally, which removes the need for high bandwidth connectivity to stream video to AWS for analysis.

    Read the Cost Optimization whitepaper 
  • The proposed reference architecture diagram uses AWS Serverless services to have a sustainable approach; the multiple options for edge compute also facilitate choosing the most appropriate service, which helps to support sustainability.

    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.

[Content Type]


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


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?