PN 1001933 rev 2
© NimbeLink Corp. 2022. All rights reserved.
28
If the connection is successful, the terminal should respond with "
CONNECTED
" followed
by some information about the connection, including the server certificate. To further
test the connection, type the following command, followed by the sequence "
CTRL+M,
CTRL+J
":
GET /things/AWS_TEST_THING/shadow HTTP/1.1
Remember to replace the "
AWS_TEST_THING
" string with the unique "thing" name
The server should respond with something similar to:
HTTP/1.1 200 OK
content-type: application/json
content-length: 383
date: Tue, 24 Jul 2018 22:35:57 GMT
x-amzn-RequestId: 6ae1eb60-6910-9a7b-e8b0-6c6d2904e239
connection: keep-alive
{"state":{"desired":{"string1":"TLS Connect to AWS","string2":"Using
the built-in stack","string3":"of the BG96"},"delta":{"string1":"TLS
Connect to AWS","string2":"Using the built-in stack","string3":"of
the
BG96"}},"metadata":{"desired":{"string1":{"timestamp":1532463231},"st
ring2":{"timestamp":1532463231},"string3":{"timestamp":1532463231}}},
"version":19,"timestamp":1532471757}
If a valid connection can be established, then it is safe to say that the certificates are
indeed valid, and thus are not the source of the problem.