This Guidance provides a set of artifacts that will guide customers in building a production monitoring architecture with AWS IoT TwinMaker and supporting services. The artifacts in this Guidance provide sample demo projects, data simulators, and articles that offer support for using various feature sets within AWS IoT TwinMaker and AWS IoT SiteWise. With AWS IoT TwinMaker, customers can get a 3D model of their plant operations derived from computer-aided design (CAD) or reality capture models, such as Matterport. Using AWS IoT TwinMaker’s Knowledge Graph, customers can view relationships between industrial assets and operations.

Please note: [Disclaimer]

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.

  • AWS CloudFormation enables end users to automate and standardize infrastructure deployment, helping ensure consistent AWS resource provisioning for AWS IoT SiteWise, AWS IoT TwinMaker, and other supporting services. This helps you minimize manual errors and operational drift for simulation and brewery demonstration environments. GitHub streamlines code changes and responses to events with features like GitHub Actions and near-real-time notifications. Together, CloudFormation and GitHub bolster operational excellence by automating workflows, swiftly reacting to system events, and maintaining standardized operations.

    Read the Operational Excellence whitepaper 
  • AWS Identity and Access Management (IAM) allows precise control over user and service permissions to permit only authorized access to resources and to maintain data confidentiality and integrity. IAM roles allow access from Grafana on the AWS IoT TwinMaker Workspace that are in line with the AWS IoT TwinMaker service documentation. Amazon Elastic Compute Cloud (Amazon EC2) instances for simulation are assigned an IAM instance role with access to AWS Systems Manager to support up-to-date patching. Systems Manager provides tools for consistent configuration management, patching, and auditing of resources, enhancing system and data protection. IAM and Systems Manager bolster security by offering granular access controls and a suite of management tools to detect and respond to security events.

    Read the Security whitepaper 
  • With AWS IoT SiteWise and AWS IoT TwinMaker, throttling limits are in place for data ingress and egress to assure continued operation. With the Managed Grafana console, you’ll have access to a workspace to visualize and analyze metrics, logs, and traces without having to build, package, or deploy any hardware or infrastructure. Managed Grafana automatically provisions, configures, and manages the operations of the workspace with automatic version upgrades. The service auto scales to meet dynamic usage demands. This is critical for handling peak usage during site operations or the start of a shift for industrial operations. As part of this Guidance, a self-managed Grafana instance is used for testing purposes.

    Read the Reliability whitepaper 
  • This architecture enables organizations to scale the deployment of their industrial digital twins across multiple sites within throttling limits. AWS Regions are configurable in the CloudFormation templates, supporting global deployments where data sovereignty requirements exist. As the number of connected assets grow, the architecture can help assure that it will scale with this growth and remain performant.

    Read the Performance Efficiency whitepaper 
  • AWS IoT SiteWise and AWS IoT TwinMaker are cost-optimized, managed services that provide customers with digital twin capabilities at the lowest possible price point. AWS IoT SiteWise and AWS IoT TwinMaker pricing is pay-as-you-go, which means you are charged only for the data that is ingested, stored, and queried. AWS IoT SiteWise contains optimized storage settings that can be configured to move data from a hot tier to cold tier in Amazon Simple Storage Service (Amazon S3).

    For the simulation, the scripts have been optimized to enable them to run on a t2.micro instance. This is available on the AWS Free Tier so you can explore the Guidance prior to connecting real sensor data streams.

    Read the Cost Optimization whitepaper 
  • With AWS IoT SiteWise, you can apply a deadband to your OPC-UA source property groups to filter out and discard certain data instead of sending it to the AWS Cloud. A deadband specifies a window of expected fluctuations in the incoming data values from your OPC-UA source. If the values fall within this window, your OPC-UA server won't send it to the AWS Cloud. You can use deadband filtering to reduce the amount of data you're processing and sending to the AWS Cloud.

    In addition, the AWS IoT SiteWise cold tier uses Apache Parquet format in Amazon S3. It is an open source, column-oriented data file format designed for efficient data storage and retrieval.  

    Read the Sustainability whitepaper 

Implementation Resources

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?