Page 11 of 42
$ aws_config --register_thing yourThingName
2019-03-28 15:26:31,265 aws_config INFO Creating certificate and keys for
yourThingName
2019-03-28 15:26:31,312 aws_config INFO Registering yourThingName into AWS
2019-03-28 15:26:31,591 credentials INFO Found credentials in shared
credentials file: ~/.aws/credentials
2019-03-28 15:26:34,962 aws_config INFO Saving certificate and key files
for yourThingName
2019-03-28 15:26:34,963 aws_config INFO Creating default device shadow
yourThingName
{
"metadata": {
"desired": {
"device_status": {
"last_log_file_read_pos": {
"timestamp": 1553786796
}
}
}
},
"state": {
"desired": {
"device_status": {
"last_log_file_read_pos": 0
}
}
},
"timestamp": 1553786796,
"version": 1
}
Note that
should be unique for each tracker board being registered. Upon completion, the following new files should be visible in
yourThingName
the certificates directory:
$ ls -la yourThingName.*
-rw-rw-r-- 1 liamw liamw 1135 Mar 28 15:26 yourThingName.cert
-rw-rw-r-- 1 liamw liamw 1704 Mar 28 15:26 yourThingName.key
-rw-rw-r-- 1 liamw liamw 451 Mar 28 15:26 yourThingName.pubkey
The file
is an automatically generated file. It is the device certificate that has now been installed into your
yourThingName.cert
AWS account against the new thing called
. Associated with this device certificate is the device's private key called
yourThingName
you
. Both these files must now be registered into the plastic tracker's cellular modem as outlined in the following
rThingName.key
section.
Arribada Horizon ARTIC R2 Developer’s Kit | User Manual