Cloud license and architecture plan

Hi, we are thinking of moving to a cloud version, have some questions:

  1. If the Ignition license is procured via AWS Marketplace, can the solution be scaled across multiple EC2 instances without incurring additional licensing costs?

  2. Can Ignition gateway be deployed on ECS (Docker containers) instead of EC2 instances?

  3. If opting to architect the solution independently, what licensing plan allows for horizontal scaling without extra fees?

  4. Is it feasible to install Ignition and the license on an EFS shared among all servers to leverage the license effectively?

Talk to your sales engineer. We're just a bunch of users.

You might check the title of your post. It looks odd!

1 Like

While you wait, I'm pretty sure the answers are:

  1. No.

  2. No.

  3. No.

  4. No.

Ignition is licensed per gateway. Ignition's cloud edition is simply a convenient way to pay on a usage or annual basis for a select set of features.

If you scale up to multiple gateways, you will pay for them.

3 Likes

Thank you so much, I will check!

Yes, I think the administrator fixed the title, I hate auto-correction :joy:

Thank you. I assume that will be the answer, but I will try my luck.

We're working on a version of Ignition Cloud Edition that will be able to run in ECS/EKS containers (and have a similar usage-based pricing to the existing VM-based Cloud Edition offering). When released, it will still be priced on a per-gateway basis.

3 Likes