search

aws-samples / aws-appsync-iot-core-realtime-dashboard

This sample application demonstrates a React based web dashboard receiving real-time updates from IoT sensors. The solution is built with AWS AppSync, AWS Amplify, Amazon Location Service, and AWS IoT Core technologies.
MIT No Attribution
114 stars 31 forks source link

Deploying stack results in a seemingly unused DynamoDB Table #15

Closed ghost closed 3 years ago

ghost commented 3 years ago

Greetings,

When I run this stack in my account, I see a DynamoDB Table created with a name like SensorValue-{generated}-dev, but when I create some sensors and simulate them, I never see any items added to the Table..

I can see the incoming events in the following places though:

Could somebody carify what purpose this Table serves here?

dave-moser commented 3 years ago

The application logs all of the sensor readings into the DynamoDB table. When the Lambda function calls the AppSync mutation, the values are logged in the table. You see no Items in the table? Do you see the Lambda function being executed successfully?

ZaLiTHkA commented 3 years ago

Hi Dave, thanks for getting back to me.

note: I'm in the process of ditching my secodary GitHub account (agreeff), so please excuse the response from different account here.

Interestingly, I did eventually see items in the database, but that came up during an "initial POC demo" with my work colleagues on Tuesday. We were going through a dummy system to investigate a few things, and I was telling them about this DynamoDB Table while I was navigating to the AWS Console page and as I said "for some reason it's always empty", it loaded and suddenly there were thousands of entries (all from my testing). Honestly not sure how or why it happened like this..

Either way, over the past week our own little proof of concept design has now morphed into something different, so I no longer have this same architecture any more. As such, I think this issue should probably be closed off for now then.

Considering I'm still in the early days of my AWS adventure, this is very likely due to something that I did incorrectly anyway. 🤦🏼