• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 91 subscribers
  • Views 618 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 287059
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

mqtt-bridge-mosquitto as t2.micro

Simon

Hello,
in an effort to downsize the EC2 instance from t3.small to t2.micro (nrfcloud-mqtt-bridge/MqttBridgeCluster/DefaultAutoScalingGroup),
the bridge instance is detached from auto scaling group then stopped.

After restart (no auto scaling), the nrfcloud-mqtt-bridge is no longer relaying data from nrfcould.

Is there an additional command needed to get the installed bridge on EC2 running again after restart?
I did a quick check to see if the bridge service was working before downsizing and it was running ok.

thank-you,

Parents Reply Children
  • 0 in reply to Øyvind

    Hello, 

    Was there a reason for why you marked the ticket with verified answer?

    The short answer from our nRF Cloud team is to no do it that way. Is there a reason for why you want to do this? The best solution to solve this, is to just remove / redeploy the example, rather than figuring out how to get it working again

    Kind regards,
    Øyvind

  • 0 in reply to Øyvind

    Moving from new ticket (287188) due to previously ticket. Should now be open again.


    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,

Related
Terms of service