Skip to main content

AWS Solutions Library

Guidance for Integrating Ignition SCADA on AWS

Overview

This Guidance demonstrates how to host and extend the Ignition Cloud Edition Supervisory Control and Data Acquisition (SCADA) software on AWS. You can use this Guidance as a framework to ingest operational technology (OT) data into a secure, scalable, and fault-tolerant Ignition Cloud Edition environment. The Ignition deployment spans two Availability Zones and uses various AWS services for data storage and data processing. It also can be extended to use artificial intelligence and machine learning (AI/ML) technologies for enterprise-level advanced analytics.

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.

The AWS services used for this Guidance provide you with a comprehensive, cloud-native framework to extend your on-premises Ignition deployments. By treating infrastructure as code, using scalable data and analytics services, and enabling edge machine learning capabilities, you can enhance operational visibility, responsiveness, and optimization across your industrial environments.

Read the Operational Excellence whitepaper 

This Guidance, when deployed on AWS, uses several services to enhance your overall security posture. These include AWS Identity and Access Management (IAM) for controlling access, AWS Key Management Service (AWS KMS) for protecting data, an d AWS IoT Core for secure communication. These services work in concert to fortify the deployment with robust access control, data protection, and secure connectivity throughout the Guidance.

Read the Security whitepaper 

Elastic Load Balancing (ELB) routes traffic requests from users' desktop and mobile applications to only the healthy Amazon Elastic Compute Cloud (Amazon EC2) instances, so that traffic is not directed to instances that are nearing overload. This approach reduces the likelihood of application failure, allowing users to seamlessly browse the mobile storefront without encountering downtime errors.

Read the Reliability whitepaper 

Aurora , configured in a multi-Availability Zone (multi-AZ) deployment, provides a highly available and fault-tolerant database infrastructure so that the Ignition SCADA system can continue operating efficiently. Additionally, the Application Load Balancer is employed to distribute traffic across multiple Ignition frontend instances so that the system can handle increased loads and traffic patterns efficiently. 

Read the Performance Efficiency whitepaper 

Amazon S3 is used for data storage, as it offers a range of storage classes , including Standard, Infrequent Access, and Glacier, among others, allowing for the optimization of costs based on the specific data access patterns and durability requirements of the Guidance. The multi-AZ deployment of Aurora is used for its capability to scale the database tier up or down based on demand, thereby avoiding over-provisioning and minimizing costs.

Read the Cost Optimization whitepaper 

SageMaker is a fully managed service for building, training, and deploying machine learning models, allowing you to optimize resource utilization and minimize the environmental impact associated with manual processes and inefficient resource management. Amazon S3 offers different storage classes that are optimized for various data access patterns and durability requirements so you can minimize the resources needed for data storage and reduce the associated environmental impact.

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.