Best way to set up dev, staging and prod environments in LoRaWAN?

Question

I'm trying to figure out the best way to separate environments for AWS IoT LoRaWAN.  I'd like to have `dev`, `staging` and `prod` separation, but haven't quite figured out how best to implement.

My complete service includes Lambda, SNS, SQS and Dynamo, which I think should be easy enough to separate.  But I'd like to be able to do the same for Wireless.

Does this have to be done with completely isolated AWS accounts?  Also, with custom IoT Core domains is it possible to create multiple custom domains like dev-iot.mydomain.com, stg-iot.mydomain.com and iot.mydomain.com?

Greg_B · Accepted Answer

It doesn't have to be done that way, but it's generally what we recommend. High level guidance here: https://docs.aws.amazon.com/whitepapers/latest/organizing-your-aws-environment/organizing-your-aws-environment.pdf

In the case of a LoRaWAN workload, I think you would probably have a separate pool of devices and gateways for each environment.

As for the IoT Core custom domains question, yes. However, are you asking in regards to your LoRaWAN workload? You can't create custom domains for the LoRaWAN endpoints (LNS and CUPS) at this time. Your LoRaWAN devices aren't provisioned with the endpoints. Only your gateways are.

Best way to set up dev, staging and prod environments in LoRaWAN?

Relevant content