@AWS IoT @nolansingroy I followed the instructions to the letter. I see the data values coming in to IoT core MQTT test client. But when I run the Query editor inTimestream I don't see any values being stored. I get a message in output tab saying success and 0 rows effected. Any advice?
Why do you specify days 500 in the x509 -req -in verificationCert.csr -CA rootCA.pem -CAkey rootCA.key -CAcreateserial -out verificationCert.pem -days 500 -sha256 call please?
AWS fleewise is the worst product of Amazon, we decided to drop it completely due its number of massive bugs and slow performance, it does not come with any DBS and just pure headache to manage signal catalogue - I suggest if you need a serious solution to look somewhere else there are a TON of better software out there
Based on changes in AWS since this video was made, some errors are occurring following this procedure: 1) Timestream does not like the timestamp produced by AWS and throws this error "errorMessage": "Failed to write records to Timestream. The error received was 'Invalid timestamp value ''. Length should be in [1, 256] in UTF-8 encoded bytes.'. 2) Grafana is now managed through a workspace so the setup procedures are more involved.
Looks like a very deep and broad dive into end-to-end IoT on AWS! For those who may find the hardware-build portion a little too deep, one of the ready-made car kits might substitute. Amazon shows several Raspberry Pi car kits (ex. Freenove); I'm working with a Freenove ESP32 board kit, and their documentation and support is passable. If the author has suggestions for ready-made hardware, it would be helpful.
Thank you so much for this great lesson. I have a question, viz. Would each device have a separate unique Certificate embedded in it before it is replaced by the JITP workflow? If yes, how could this be achieved? or could it be that all devices carry the same signed certificate, which would uniquely be replaced on the device's first attempt to connect to AWS IoT core JITP workflow?
Each device would have a unique certificate that is flashed on by the manufacturer through something like programmable memory. Devices all carrying the same signed certificate is a security risk as devices that never undergo the JITP workflow could potentially be compromised.
If each device comes with unique certificate, what then is the need for it to be replaced with a new one with the JITP mechanism, isn't that redundancy?
@@AjirogheneSunny It is not necessarily being replaced. It is being activated on the cloud side. The private key is what really matters here as it is used to generate the certificate, so as long as that is unique, then you mitigate the security risk.
Got all the way through, got data in timestream, but upon opening the Grafana dashboard, I have no option to add data source nor much else really. Any advice?
The specific workshop link above returns “Page not found”, as does the page returned by searching for “iot robot” in AWS Workshops. Can this be fixed? Is anyone monitoring this channel?
Very good video! Looking forward to the 3rd part which is exciting. I hope to see model training process as well, for example, checking if light is on or not, door is closed or open, etc.
This is a very practical guide. Nice job! thanks. One quick question, if I use 360 GoPro camera, can I directly use GoPro to connect to kinesis Stream?
Its a very nice information, here I'm able to stream with webrtc same using your video, I have one question that I need to do, How we can record video in kinesis webrtc over the raspberry pi?
Should video ingested with this GreenGrass Edge Agent deployment work with S3 Delivery on the KVS stream? S3 Delivery works when using the KVS Producer app at the edge, but when using this GG solution, the S3 delivery does not seem to work. Is there something special I need to configure in the GG deployment?
How challenging would it bo to implement 2 way audio and control a few accessories instead of the object recognition ? I know I should be able to do they with WebRTC.
