1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Hi Sidd. You said you use the same code as that question. Some points:
- have you created a Thing named ESP8266 in AWS IoT Core?
- have you created a certificate and private key and installed them on your device?
- is that certificate registered in AWS IoT Core, activated, and attached to your ESP8266 Thing?
- are you using the same IoT policy as shown in that other question? is it attached to your certificate? (please be aware that the policy shown in that other question is setup for the ap-south-1 region and it has a fake account number.)
- is the MQTT_HOST value in your firmware correct for your account and region?
Have you enabled CloudWatch logging? https://docs.aws.amazon.com/iot/latest/developerguide/monitoring_overview.html Do you have any errors in CloudWatch?
- Yes, I have created, the thing and attached the policy accordingly. 2.Yes installed the certificate while creating the thing.
- I'm not sure about the third point. How to do that, it is attached to thing I think?
- Yes using the same value. 5.Yes copied it directly from the settings.
Issue may be in 3, 4 point I think.
In place of resource ARN I have given '*' , so that It allows everything.
The policy needs to have your region and your account number (if you use the specific policy from the other question).
To check certificate and policy attachment: AWS IoT Core console->All devices->Things->ESP8266->Certificates you should see the ID of the right certificate and Status should be Active. Then click on the Certificate ID and you should see the attached policies.
Hi Greg it worked , thanks for helping.
Contenuto pertinente
AWS UFFICIALEAggiornata 2 anni fa- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
I am using the same code as mentioned here, In my console, I am not able to connect with AWS. Please see the thread I have added images there too. https://repost.aws/questions/QUmMfkh_RUQPKviKPSsZm0pQ/esp-8266-keeps-disconnecting-with-aws-iot-getting-client-error