reference deployment

Ignition by Inductive Automation on AWS

Standalone or cluster deployment of Ignition industrial automation servers

View deployment guide

This Partner Solution deploys Ignition by Inductive Automation to the Amazon Web Services (AWS) Cloud. It provides standalone and cluster deployment options of Ignition on Amazon Elastic Compute Cloud (Amazon EC2) Linux instances. Both options are designed to be secure and highly available, configured with best practices for security, network gateway connections, and database connectivity.

Inductive Automation Ignition logo

This Partner Solution was developed by Inductive Automation in collaboration with AWS. Inductive Automation is an AWS Partner.

  •  What you'll build
  • Standalone architecture

    The standalone deployment option sets up the following:

    • A highly available architecture that spans two Availability Zones.*
    • A virtual private cloud (VPC) configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.*
    • In the public subnets:
      • Managed NAT gateways to allow outbound internet access for resources in the private subnets.*
      • (Optional) Linux bastion hosts in an Auto Scaling group to allow inbound Secure Shell (SSH) access to Amazon EC2 instances and Aurora database in the private subnets.*
      • (Optional) An AWS Client VPN configuration to allow direct access to Amazon EC2 instances and Aurora databases in the private subnets (not shown).*
      • A primary and secondary Ignition server in the first and second Availability Zones, respectively. 
    • In the private subnets, an Amazon Aurora DB cluster in a security group containing the following:
      • A primary DB instance supporting write operations.
      • Two replica DB instances supporting read operations.
    • AWS Key Management Service (AWS KMS) to enable encryption at rest for the Aurora DB cluster.
    • Amazon CloudWatch for a bastion host CPU usage alarm.
    • Amazon Simple Notification Service (Amazon SNS) to send notifications when the CloudWatch alarm is invoked.

    * The template that deploys the Partner Solution into an existing VPC skips the components marked by asterisks and prompts you for your existing VPC configuration.

    Cluster architecture

    The cluster deployment option sets up the following:

    • A highly available architecture that spans two Availability Zones.*
    • A VPC configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.*
    • In the public subnets:
      • Managed NAT gateways to allow outbound internet access for resources in the private subnets.*
      • (Optional) An AWS Client VPN configuration to allow direct access to Amazon EC2 instances and Aurora databases in the private subnets (not shown).*
    • In the private subnets:
      • A primary and backup Ignition backend server in the first and second Availability Zones, respectively.
      • An Ignition frontend server in each Availability Zone.  
      • An Aurora DB cluster in a security group containing the following:
        • A primary DB instance supporting write operations.
        • Two replica DB instances supporting read operations.
    • An Application Load Balancer configured with an Amazon SSL certificate to route traffic to Ignition frontend servers in the private subnets.
    • AWS KMS to enable encryption at rest for the Aurora DB cluster.
    • CloudWatch for a bastion host CPU usage alarm.
    • Amazon SNS to send notifications when the CloudWatch alarm is invoked.
  •  How to deploy

  • To deploy this Partner Solution, follow the instructions in the deployment guide, which includes these steps.

    1. Sign in to your AWS account. If you don't have an account, sign up at https://aws.amazon.com.
    2. Purchase an Ignition license from Inductive Automation. You can run Ignition for a two-hour trial period without a license.
    3. Launch the Partner Solution. The stack takes about 1 hour to deploy. Before you create the stack, choose the AWS Region from the top toolbar. You can choose from the following options:
    4. Connect to the Igntion web console.

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on this solution.  

    View deployment guide for details
  •  Costs and licenses

  • This solution requires an Ignition license from Inductive Automation. Refer to inductiveautomation.com/pricing/ignition or contact your Inductive Automation representative. You can use Ignition for a two-hour trial period without a license.

    You are responsible for the cost of the AWS services and any third-party licenses used while running this solution. There is no additional cost for using the solution.

    This solution includes configuration parameters that you can customize. Some of these settings, such as instance type, affect the cost of deployment. For cost estimates, refer to the pricing pages for each AWS service you use. Prices are subject to change.

    Tip: After you deploy a solution, create AWS Cost and Usage Reports to track associated costs. These reports deliver billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your account. They provide cost estimates based on usage throughout each month and aggregate the data at the end of the month. For more information, refer to What are AWS Cost and Usage Reports?