# Node-Red installation in AWS

**URL:** <https://discourse.nodered.org/t/node-red-installation-in-aws/90555>\
**Category:** General\
**Tags:** docker\
**Created:** [30 August 2024 12:21 UTC](https://discourse.nodered.org/t/node-red-installation-in-aws/90555 "2024-08-30T12:21:26Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![bobfield](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bobfield/32/83723_2.png) [@bobfield](https://discourse.nodered.org/u/bobfield)\
**Post date:** [30 August 2024 12:21 UTC](https://discourse.nodered.org/t/node-red-installation-in-aws/90555/1 "2024-08-30T12:21:26Z")

</div>

I intend to create a new instance in my AWS account to install Dashboards on Node-Red. I have a Dashboard for each client. What is the best and most economical implementation strategy? Create an AWS instance for each customer, or create a single AWS instance and use Docker to instantiate the customers?

Thanks,

Roberto

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [30 August 2024 12:27 UTC](https://discourse.nodered.org/t/node-red-installation-in-aws/90555/2 "2024-08-30T12:27:41Z")

</div>

Have you looked at Flowfuse?

---

<div class="post-metadata">

**Author:** ![bobfield](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bobfield/32/83723_2.png) [@bobfield](https://discourse.nodered.org/u/bobfield)\
**Post date:** [30 August 2024 12:56 UTC](https://discourse.nodered.org/t/node-red-installation-in-aws/90555/3 "2024-08-30T12:56:48Z")

</div>

Yes Paul. I know about Flow Fuse, and I think that is the best solution for me. But I'am a startup and I have AWS credits to use with no paid. Then at the moment I think that is the more economical estrategy for me.

Thanks,

Roberto

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [30 August 2024 15:08 UTC](https://discourse.nodered.org/t/node-red-installation-in-aws/90555/4 "2024-08-30T15:08:03Z")

</div>

There is a third option, it is possible to run multiple instances of node-red without using docker, each with a different user directory and port.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [30 August 2024 15:11 UTC](https://discourse.nodered.org/t/node-red-installation-in-aws/90555/5 "2024-08-30T15:11:58Z")

</div>

If you can, I would certainly try to run each customer in their own instance since that will make charging and management of resources a lot easier I would think.

I'm not so familiar with AWS, but in Azure, you would generally create separate subscriptions to segment groups of services and charges. I assume that AWS has something similar.

You would also create segmented networking to absolutely ensure that customer network traffic never overlaps.

---

<div class="post-metadata">

**Author:** ![bobfield](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bobfield/32/83723_2.png) [@bobfield](https://discourse.nodered.org/u/bobfield)\
**Post date:** [31 August 2024 11:23 UTC](https://discourse.nodered.org/t/node-red-installation-in-aws/90555/6 "2024-08-31T11:23:15Z")

</div>

Thanks Julian,

I will see this option.

---

<div class="post-metadata">

**Author:** ![bobfield](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bobfield/32/83723_2.png) [@bobfield](https://discourse.nodered.org/u/bobfield)\
**Post date:** [31 August 2024 11:25 UTC](https://discourse.nodered.org/t/node-red-installation-in-aws/90555/7 "2024-08-31T11:25:58Z")

</div>

Thanks Colin,

It seems like a good solution to me. It simplifies not having to use docker. I will analyze it.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [31 August 2024 14:27 UTC](https://discourse.nodered.org/t/node-red-installation-in-aws/90555/8 "2024-08-31T14:27:56Z")

</div>

> [@bobfield](#):
>
> Yes Paul. I know about Flow Fuse, and I think that is the best solution for me. But I'am a startup and I have AWS credits to use

You know can run FlowFuse self hosted too 🤷‍♂️ there are setup scrips, helm charts and everything you need , already written to avoid having to reengineer 3y of work that has gone into FlowFuse to make running node-red securely at scale. You know we have a bug bounty scheme and are very proactive with security reports etc.

Maybe worth a chat with @zackwasli ?

---

<div class="post-metadata">

**Author:** ![bobfield](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bobfield/32/83723_2.png) [@bobfield](https://discourse.nodered.org/u/bobfield)\
**Post date:** [1 September 2024 10:12 UTC](https://discourse.nodered.org/t/node-red-installation-in-aws/90555/9 "2024-09-01T10:12:44Z")

</div>

Hi Steve,

I understand. But I believe that later on, when my needs with Node-Red are more consolidated.

Thanks

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [30 November 2024 10:12 UTC](https://discourse.nodered.org/t/node-red-installation-in-aws/90555/10 "2024-11-30T10:12:49Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.