Persisting AWS IoT Config Between Flashes
Hey all, I've been exploring Mongoose OS on an ESP8266 for use in an upcoming internal product and it's been great so far. I'm using
mos flash, and
mos aws-iot-setup to handle the firmware compilation and AWS provisioning steps, but every time I
flash a new firmware, the system falls back to whatever default settings that don't work with AWS.
I've tried dumping some of the config files after
mos aws-iot-setup gets run and adding those to my configs along with some certs for testing, but it always fails to use software ECDSA to connect (I haven't set up an ATECC508A module yet).
The ideal workflow I'm building towards would be:
- Send a copy of the firmware to PCB Assembly house
- Use a build script flashes/tests our production firmware
- Provision the device with a limited AWS policy
- At some point in the future, call the Mongoose OS RPC over MQTT (through AWS) to initiate an OTA update
If there's a better way to do any of this, I'd love to hear it, I'm just working off of what I've found reading through the codebase and your documentation.