# Node-RED AWS issue

**URL:** <https://discourse.nodered.org/t/node-red-aws-issue/82183>\
**Category:** General\
**Tags:** http-in\
**Created:** [19 October 2023 10:15 UTC](https://discourse.nodered.org/t/node-red-aws-issue/82183 "2023-10-19T10:15:35Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [19 October 2023 10:29 UTC](https://discourse.nodered.org/t/node-red-aws-issue/82183/4 "2023-10-19T10:29:41Z")

</div>

The `HTTP IN` node does not spawn a new express instance, it will use the same instance that Node RED is using, but with a different route (as configured in the configuration of the node).

So using a domain or not - you will need to specify a port on client devices.

That's not to say you can't use some form of tunnel/port forward to hide the true port - but you will need to research your options.

And remember to give this a read. 😉  
[Safely accessing Node-RED over the Internet - FAQs - Node-RED Forum (nodered.org)](https://discourse.nodered.org/t/safely-accessing-node-red-over-the-internet/45024)

---

_[View the full topic](https://discourse.nodered.org/t/node-red-aws-issue/82183)._