PN 1001933 rev 2
© NimbeLink Corp. 2022. All rights reserved.
27
6. Troubleshooting
6.1 HTTP Response Codes
6.1.1
403 Forbidden
If a connection can be established, but the AWS response to the "
GET
" command is "
403
Forbidden
", make sure that the current AWS policy is set to allow all IoT actions. This
can be done through the AWS IoT Console.
6.1.2
400 Bad Request
If a connection can be established, but the AWS response to the "
GET
" or "
POST
"
command is "
400 Bad Request
", make sure the syntax of the "
GET
" or "
POST
" command
is correct.
6.2 Verify Credentials
If for some reason the credentials for the AWS connection do not work,
used to check their validity. This process is helpful for narrowing down the source of the
connection issue.
6.2.1
Testing AWS Credentials using OpenSSL
To test credentials with OpenSSL, first ensure that OpenSSL is properly installed on a
Linux or Windows system. Next, navigate to the directory that contains the certificates
that are being tested. Issue the following command to attempt a connection to AWS:
openssl s_client -servername
a272...amazonaws.com
-connect
a272...amazonaws.com
:8443 -CAfile
VeriSign-Class\ 3-Public-Primary-Certification-
Authority-G5.pem
-cert
8da6fe87f3-certificate.pem.crt
-key
8da6fe87f3-
private.pem.key
-certform PEM -keyform PEM
Be sure to replace any of the text in bold with unique certificate names, and the unique
AWS endpoint URL.