Deploy Inductive Automation Ignition on ZEDEDA

Updated

Introduction

Inductive Automation Ignition is an integrated software platform for SCADA, IIoT, and MES systems. You can deploy this application on an edge node to collect data, control processes, and modernize operations in disconnected or industrial environments. 

This article walks through deploying Inductive Automation Ignition (Edge) on ZEDEDA using a container-based Edge App and cloud-init for zero-touch configuration. The structure mirrors proven ZEDEDA deployment patterns used for third‑party applications (volumes, networking, cloud‑init, and validation).

Prerequisites

  • You have onboarded your edge node. 
  • The edge node must be running a supported version of EVE-OS.
  • Outbound HTTPS (port 443) connectivity is required.
  • You have either the SysManager or SysAdmin role in your ZEDEDA Cloud enterprise.
  • After onboarding is complete, your edge node will appear as Active under Edge Nodes > Devices in the ZEDEDA dashboard.

Architecture Overview

  • Platform: ZEDEDA (ZedControl + EVE‑OS)
  • Application: Inductive Automation Ignition (Edge) Zededa Global Marketplace
  • Deployment Type: Standalone container
  • Configuration Injection: cloud-init
  • Networking: ZEDEDA virtual networking with explicit inbound port mappings

Import and Clone the App Configuration

  1. Go to Marketplace > Edge Apps > Global Edge Apps to import the configuration to Local. 
  2. To clone:
    1. From Marketplace > Edge Apps > Local Edge Apps, click the app card.
    2. Click the ellipsis (⋯).
    3. Click Clone.
    4. Modify any CPU, RAM, or network settings.

Assign Identity and Drives

Attribute  Value
Name / Title Ignition
Deployment Type Standalone
Container Mode Standard
CPUs 4
Memory 4 GB
CPU Pinning Disabled

Assign Network Interfaces

From Interfaces:

  1. Check Configure Interfaces for this edge app.
  2. To assign eth0 as the management interface, select Virtual Network Interface. 
  3. WLAN adapters may remain unassigned unless explicitly required

Confirm IP assignment under Environment after deployment.

Configure Network Access

Ignition requires multiple inbound ports depending on the features enabled.

Outbound Rules:

Host/IP Protocol  Port Action
0.0.0.0/0 ANY ANY Allow

Inbound Rules:

IP Address Protocol Edge Node Port App Port Action
0.0.0.0/0 TCP 8088 8088 Map
0.0.0.0/0 TCP 8043 8043 Map
0.0.0.0/0 TCP 8060 8060 Map

Port descriptions:

  • 8088 – Ignition Gateway (HTTP)
  • 8043 – Ignition Gateway (HTTPS)
  • 8060 – Ignition Edge services

Add Cloud-Init Configuration

Ignition supports environment‑variable based bootstrap. ZEDEDA cloud‑init is used to inject these values at first boot.

  • Name: cloud-init
  • Variable Delimiter: ###
  • Allow Edge App to set entire configuration: No

Example:

#cloud-config
runcmd:
- export IGNITION_EDITION=edge
- export GATEWAY_ADMIN_USERNAME=admin
- export GATEWAY_ADMIN_PASSWORD=password
- export ACCEPT_IGNITION_EULA=Y
- export IGNITION_LICENSE_KEY=<your-license-key>
- export IGNITION_ACTIVATION_TOKEN=<your-activation-token>

Notes:

  • The license key OR activation token can be used
  • Do not hardcode secrets in production—use ZEDEDA secrets when available

Deploy

Now you’re ready to deploy the Plate Recognizer Stream container to your device.

  1. Go to Marketplace > Local Edge Apps > Your Ignition App.
  2. Click Deploy.
  3. Choose Project: your project, Edge Node: your onboarded device, Deployment Type: Container.
  4. Apply cloud-init configuration.
  5. Verify resource allocation: 4 vCPU / 4 GB RAM.
  6. Click Deploy.

Validate

Check Runtime Status

  • Navigate to Edge App Instances → Logs
  • Confirm Ignition startup messages

Access Ignition UI

  • HTTP: http://<device-ip>:8088
  • HTTPS: https://<device-ip>:8043

Log in using the admin credentials provided in cloud‑init.

Hardware Sizing Recommendations

Use Case CPU Memory
Ignition Edge 2-4 vCPU 4 GB

Actual sizing depends on the following:

  • Tag count
  • OPC connections
  • Modules enabled
  • Historian load

Common Issues and Fixes

  • If the UI is not reachable, the root cause is unmapped ports. Verify the inbound rules.
  • If the license is not applied, the issue is an invalid key or token. Recheck the cloud-init configuration. 
  • If the application is stuck starting, the root cause is insufficient memory. Increase the allocated RAM.

Conclusion

This deployment model enables:

  • Zero-touch provisioning
  • Deterministic, repeatable installs
  • Secure configuration injection
  • Centralized lifecycle management

Ignition + ZEDEDA is a strong fit for industrial edge, OT modernization, and disconnected environments.

For advanced patterns (HA, Edge Sync, air‑gap, or OPC‑UA segmentation), extend this baseline.

Was this article helpful?
0 out of 0 found this helpful