Skip to main content

AWS Solutions Library

Guidance for Supply Chain Control Tower Visibility on AWS

Overview

This Guidance demonstrates how AWS Supply Chain Control Tower can improve visibility into business-critical systems. Analyze a constant stream of data in near real-time to determine actionable insights and predictive recommendations for your supply chain.

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.

Download the architecture diagram

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.

By solely leveraging AWS managed services, each service emits its own set of metrics into Amazon CloudWatch, where customers can monitor for errors.

Read the Operational Excellence whitepaper 

For public facing services (such as the UI), Amazon Cognito is used to ensure secure access to the core applications and services - this includes role-based access controls. Provisioned API endpoints are also secured with appropriate access, authentication, and authorization controls to ensure use by allowed systems and users. For other AWS services, AWS Identity and Access Management (IAM) role-based access controls are leveraged to ensure least privileged access between services.

The AWS managed services used in this architecture support secure communication by encrypting data in transit. Where data is stored (such as Amazon Redshift and Amazon S3), data is also encrypted at rest.

Read the Security whitepaper 

This architecture leverages managed services that are designed to be highly available by default. Some services (such as Amazon Redshift) can also be configured to be deployed over multiple availability zones. Each component in this architecture is designed to maintain availability in the event of disaster events. AWS managed services are designed to span multiple availability zones. Other services, like Amazon Redshift, can also be deployed over multiple availability zones. In the case of availability zone failure, services deployed can continue to operate.

Read the Reliability whitepaper 

Scalable and highly available services like Amazon S3, Amazon Kinesis, AWS Glue and Amazon Redshift are purposefully built for data analytics workloads.

Read the Performance Efficiency whitepaper 

This architecture follows a serverless-first approach. Where possible, serverless services scale according to load to ensure you only pay for what is used. In addition, AWS managed services are used that allow for utility billing.  

Data transfer is a consideration for any data-orientated architecture. In this solution, the biggest data volume is ingested from source systems which is generally uncharged in the inbound direction. Data transfer for AWS SFTP file transfers, API Gateway requests, and Amazon AppFlow data are charged as per the documented service pricing. All other data is kept within the region for processing to minimize transfer charges.

Read the Cost Optimization whitepaper 

AWS managed services help to scale up and down according to business requirement and traffic, and are inherently more sustainable than on-premises solutions. Additionally, leveraged serverless components automate the process of infrastructure management and make it more sustainable.

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.