# Hosting Ignition on AWS **URL:** \ **Category:** Ignition\ **Created:** [June 30, 2020, 8:05pm UTC](https://forum.inductiveautomation.com/t/hosting-ignition-on-aws/36210 "2020-06-30T20:05:27Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![mjohnson](https://avatars.discourse-cdn.com/v4/letter/m/a9a28c/32.png) [@mjohnson](https://forum.inductiveautomation.com/u/mjohnson)\ **Post date:** [June 30, 2020, 8:05pm UTC](https://forum.inductiveautomation.com/t/hosting-ignition-on-aws/36210/1 "2020-06-30T20:05:27Z")
Currently, I have Ignition installed on AWS EC2 instance. I can launch my web page internally in a web browser with the private IP. I can not get it to launch on the public IP. Is there a setting somewhere to get it to work with the public IP? This is all with Ignition perspective/ ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [June 30, 2020, 8:21pm UTC](https://forum.inductiveautomation.com/t/hosting-ignition-on-aws/36210/2 "2020-06-30T20:21:59Z")
Nothing else should be required (I haven’t set up AWS in a while) - are you still on the default ports/are you using those ports with the public domain name? The “public” IP might only have 80/443 (default HTTP/HTTPS) ports open, if even that; it might just be a security restriction. ---
**Author:** ![mjohnson](https://avatars.discourse-cdn.com/v4/letter/m/a9a28c/32.png) [@mjohnson](https://forum.inductiveautomation.com/u/mjohnson)\ **Post date:** [July 1, 2020, 3:50pm UTC](https://forum.inductiveautomation.com/t/hosting-ignition-on-aws/36210/3 "2020-07-01T15:50:15Z")
I am using ports 1883 for the MQTT messaging between an edge device and AWS ---
**Author:** ![mjohnson](https://avatars.discourse-cdn.com/v4/letter/m/a9a28c/32.png) [@mjohnson](https://forum.inductiveautomation.com/u/mjohnson)\ **Post date:** [July 2, 2020, 4:10pm UTC](https://forum.inductiveautomation.com/t/hosting-ignition-on-aws/36210/4 "2020-07-02T16:10:56Z")
I have a firewall rule set for the IP address of the Edge device set in the AWS firewall with the 1883 port open. At the edge device, the MQTT transmission is using the public IP with port 1883. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [July 2, 2020, 4:41pm UTC](https://forum.inductiveautomation.com/t/hosting-ignition-on-aws/36210/5 "2020-07-02T16:41:20Z")
I don’t see how MQTT is related - you’re having issue reaching your gateway webpage/Perspective, right? Have you opened 80/443? Is Ignition bound to those ports, or still using its default HTTP(S) ports: 8088, 8043? AWS likely doesn’t open any ports, particularly not unusual ones like 8088/8043. ---
**Author:** ![craigb](https://avatars.discourse-cdn.com/v4/letter/c/9f8e36/32.png) [@craigb](https://forum.inductiveautomation.com/u/craigb)\ **Post date:** [July 2, 2020, 5:35pm UTC](https://forum.inductiveautomation.com/t/hosting-ignition-on-aws/36210/6 "2020-07-02T17:35:31Z")
From memory testing a AWS server for ignition there was 2 places to open ports. One as the AWS firewall accessible when you log into your account and the other was in the OS itself, in my case it was windows firewall. ---
**Author:** ![mjohnson](https://avatars.discourse-cdn.com/v4/letter/m/a9a28c/32.png) [@mjohnson](https://forum.inductiveautomation.com/u/mjohnson)\ **Post date:** [July 2, 2020, 6:00pm UTC](https://forum.inductiveautomation.com/t/hosting-ignition-on-aws/36210/7 "2020-07-02T18:00:26Z")
The webpage is another issue. Right now I just want to get the MQTT working. The web page seems to work internally and yes Ignition is bound to 8088 it seems