This Guidance helps protect OT infrastructure using cybersecurity services. As digital applications for OT have increased, so has the convergence of OT and IoT technology. However, a more complex OT network may open the way for security vulnerabilities. With this Guidance, you can implement a cybersecurity approach to defend against malicious attacks, support passive monitoring 24/7, and plan for pre-defined actions to avoid security breaches that may lead to plant shutdowns.

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.

  • ElastiCache simplifies deploying, operating, and scaling an in-memory cache in the cloud. ElastiCache is a managed service, so AWS takes care of the operational aspects of running Redis, including hardware provisioning, software patching, horizontal and vertical scaling, upgrading engine versions, automatic backup, and monitoring. 

    Read the Operational Excellence whitepaper 
  • Security Hub provides you with a centralized location to view and manage security alerts, findings, and recommendations across multiple AWS accounts and services. Security Hub in this Guidance provides managed threat intelligence based on analysis from AWS and third-party sources to identify known bad actors.

    Read the Security whitepaper 
  • Amazon RDS automatically performs backups of the database to Amazon S3. This includes daily snapshots and transaction logs captured every 5 minutes, which aids in disaster recovery. This Guidance also uses multi-Availability Zone (AZ) Amazon RDS database instances to provide automated failover to a standby replica in another AZ. This minimizes downtime if there are AZ failures.

    Read the Reliability whitepaper 
  • Amazon EKS provides Amazon CloudWatch metrics for monitoring overall cluster health, resource utilization, application performance, and bottlenecks. Amazon EKS integrates tightly with Amazon S3 and Amazon RDS in addition to caching, networking, security, and monitoring services. This integration can help you meet workload requirements around scaling, traffic management, and data access patterns.

    Read the Performance Efficiency whitepaper 
  • A data lake powered by Amazon S3 provides a highly durable and inexpensive way to store large amounts of log, packet capture, and forensic data from the Guidance over long periods of time at lower costs. Additionally, analyzing storage metrics and access patterns can help you better understand your resource usage so you can make informed decisions about optimizing frequently accessed "hot" data versus using less expensive “cold” data archives.

    Read the Cost Optimization whitepaper 
  • Amazon RDS makes it easy to right size database instance types and storage based on actual utilization data—this helps you prevent overprovisioning. Additionally, Amazon S3 provides highly durable storage, reducing how often the Guidance must replicate data for redundancy.

    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?