Closed SruthiAlajangi-AlifSemi closed 1 year ago
@sruthi1209 : I updated your post to remove private details (your AWS account ID).
Could you clarify which tutorial or demo you are following?
If you are using the create-from-csr
api call rather than the create
api call, I believe you need to modify your policy document as follows:
replace
$aws/certificates/create/*
with
$aws/certificates/create-from-csr/*
The fleet provisioning demo directory in this repository contains an Example Policy when using the create-from-csr api call.
Another useful reference for fleet provisioning using this library is located in the FreeRTOS Plus AWS Fleet Provisioning Demo, particularly DemoSetup directory which includes a script to deploy and tear down the necessary stack (including policy docs) via CloudFormation.
Closing for now. Feel free to reopen.
I am working on FreeRTOS based fleet provisioning by claim application, i am using fleet provisioning library provided in this sdk, and this mqtt interface i could connect to AWS IoT with claim credentials. When i try to subscribe to fleet provisioning topics, it is failing if i give specific resource in subscribe action of claim policy, but if i give '*' as resource for subscribe,publish&receive actions i could connect, subscribe, receive certificate and private key from AWS and also i could receive name of new thing created. Is there any other way to achieve this. Below is my claim policy where i am giving fleet provisioning by claim specific resources.