|
Our use cases are almost certainly different, but I can think of no ways I’ve had to workaround or deal with scaling. AWS seems super happy to let you use as much data as you possibly can (obviously). Yes, registration can be complex! JIT reg, JIT provision, PSK reg at birth, certs, keys, tokens. We’re even doing something really goofy because our device never touched the internet directly, always through a middleman, so it’s been double complex and revolves around custom authorization and temporary tokens. I see how we could simplify by doing JIT-R with PKI but don’t have the resources on the device. I don’t fault the providers for making it seem like it’s complex, it definitely can be! I suppose it’s annoying that a “job” in AWS costs $0.03 per device, and that can be any issued job using their API. So you “could” use their setup to reset() but mostly it’s their OTA Update agent which is good, but when you’re looking at 100k eventual devices, every firmware update is $3k. Which is also fine if it’s an update you need. If it isn’t, you threw away $3k. The OTA Agent is very good though, rollbacks, logging, canary rollout, etc. I worked right with AWS on this project so Azure or GCP wasn’t an option. And now I know the system so it’s unlikely as a small team I’ll look into Azure next time. But I guess that’s how it goes. |