mqtt-bridge-mosquitto as t2.micro pt.2

[Simon]

The solution seems to be built for a Production rollout for organizations with resources,
but not so much for devs on a tight budget.

The actual bridge build is quite extensive in AWS with many configurations, assignments and a new instance.

Other than the use of t3.small, the solution also deploys two NAT Gateways which is really taxing.
For example, the cost so far for just the first five days in April is already $12.93 of which $11.43 is Gateway.
The monthly total would be $77.58 for just a few dev tests of the bridge.

To be dev friendly, the request is to also have a dev version using a nano and a NAT Instance (pre-built by the dev).
Monthly cost would be 10x less and dev friendly.

The attempt was to first downsize the instance and then reassign the NAT from a Gateway to an Instance,
but could not get a restart on the first part.

thank-you,

=========================================
The initial ticket is locked so continuing here to make a reply.
Answer was verified then retracted when switched from github back to devzone.
https://devzone.nordicsemi.com/f/nordic-q-a/86611/mqtt-bridge-mosquitto-as-t2-micro

[Lincoln Thomas]

Hello Simon,

The MQTT Bridge example was built as something that could handle heavy load. Users are welcome to extend/change that example code however they want, and we encourage it, just like the NCS Samples that are meant as starting points for customer firmware developers. But we do not have the developer resources to make more variants of the bridge example at this time.

You seem AWS-knowledgeable enough to work through your current issue and create a lower-resourced version. If you do, you could create a GitHub fork of our repo with your code, which we could keep long-term for others to use. You'd get the credit and fame for it.

-Lincoln

[Simon]

that's nice