- Newest
- Most votes
- Most comments
Good morning rePost-User-7220504,
If I understand correctly, you are trying to build a fleet provisioning by claim scenario for a device running AWS C SDK; but the process is failing exactly at the moment you are supposed to receive your permanent certificate on your device (your device being suddenly disconnected by IoT Core). Is that accurate?
If so, there are at least 3 key things to ensure:
- The accepted/rejected certificate callback topics subscriptions should be completed before you publish to the certificate creation topic. You may introduce an explicit short delay (1 or 2 seconds) in your code for that.
- The accepted/rejected 'registerDevice' topics subscriptions should be completed before you publish to the device registration topic. You may introduce a short delay as well for that.
- You should have an existing provisioning template (that will determine your device IoT policy, group memberships, etc after registration).
Enforcing point #1 will likely solve your current main issue (not receiving final certificate on your device).
Enforcing points #2 & #3 will ensure that the rest of your device provisioning flow is completed successfully (Certificate status will change from 'Pending activation' to 'Active') and your device will be able to communicate with IoT Core and get on-boarded in groups as defined in your provisioning template. Refer to "CreateKeysAndCertificate" in official documentation here for a step by step description.
For deeper dive, you may go through this IoT Device Management Workshop series as well!
Charly
Relevant content
- asked a year ago
- Accepted Answerasked 2 years ago
- I tried to delete my ACM certificate but received an error that it's in use with other AWS resourcesAWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago