Can you please explain what will happen if the internet gets disconnected in the middle? For say, I deployed Greengrass lambda functions from the AWS cloud and my functions are running on a physical device. When the internet gets disconnected in the middle, there will be no communication between the physical device and the cloud. My question is what will happen when the internet is back? Will the Greengrass core running on the physical device communicate with the cloud automatically or do I need to restart the daemon every time?
It depends on the AWS IoT SDK implementation of the MQTT protocol. It seems like there would be a publish queue waiting for the internet to come back online. I don't think the GG Core service would quit without internet, but I have this running on EC2 for demo purposes, so I'm not sure how to test that. Physical devices are presumed to be offline, or they wouldn't need GreenGrass. They could communicate to IoT Core directly, and a disconnect would have the same issue - MQTT protocol determines the error handling. Wait and retry?
Hello sir, thank you for the video. Question: how would you edit the subscriptions to run this application locally? I am under the impression that the application sends data to the cloud in the demonstration, or am I mistaken? Thank you
Thank you for that wonderful Tutorial. It was extremely helpful and enjoyable. I wanted to clarify somehting. After deploying greengrass, you said that it was the lambda on the edge that is run during runtime, not the one in the cloud. Did you mean the Lambda that is executed is the one located in the deployment folder at the greengrass core? If this is the case, then when there is no internet (offline), then the publish/subscriptions will continue to work because of the downloaded deployment. Also, I'm wondering, what is the point of a Lambda at the cloud, versioning and storage I assume.
I built out some IoT edge infrastructure where the lambda functions deployed to GreenGrass core only performed the forwarding to IoT Core on behalf of the non-internet capable clients (GG devices) and the heavy-lifting Lambda is still hosted on AWS. The advantage of this is your main lambda function is handling both connected and disconnected client data, so it can be aggregated for analytics, for example. Most big deployments will want to handle 100,000s of clients and you wouldn't leave systems completely offline and isolated. For your own home hobby build, you might not need the cloud parts.
Thanks for the video it helps a lot. When i followed the same everything is working fine but from lambda to topic it returns empty payload even i gave raw data. Can you please help me on this.
Dunno if anyone gives a shit but if you are bored like me during the covid times then you can stream all of the new series on InstaFlixxer. I've been watching with my gf for the last months :)
Well done and thank you for sharing knowledge with developers.
Thanks a lot. it is very helpful. this one is only video which explain about AWS greengrass as simple. Thanks Again :)
Hi, Wonderful tutorial! can you share the camera make/model - Thanks.
Can you please explain what will happen if the internet gets disconnected in the middle?
For say, I deployed Greengrass lambda functions from the AWS cloud and my functions are running on a physical device.
When the internet gets disconnected in the middle, there will be no communication between the physical device and the cloud.
My question is what will happen when the internet is back? Will the Greengrass core running on the physical device communicate with the cloud automatically or do I need to restart the daemon every time?
It depends on the AWS IoT SDK implementation of the MQTT protocol. It seems like there would be a publish queue waiting for the internet to come back online. I don't think the GG Core service would quit without internet, but I have this running on EC2 for demo purposes, so I'm not sure how to test that. Physical devices are presumed to be offline, or they wouldn't need GreenGrass. They could communicate to IoT Core directly, and a disconnect would have the same issue - MQTT protocol determines the error handling. Wait and retry?
Hello sir, thank you for the video. Question: how would you edit the subscriptions to run this application locally? I am under the impression that the application sends data to the cloud in the demonstration, or am I mistaken? Thank you
Does the lambda functions requires any permissions to read from the TOpics
Thank you for that wonderful Tutorial. It was extremely helpful and enjoyable. I wanted to clarify somehting. After deploying greengrass, you said that it was the lambda on the edge that is run during runtime, not the one in the cloud. Did you mean the Lambda that is executed is the one located in the deployment folder at the greengrass core? If this is the case, then when there is no internet (offline), then the publish/subscriptions will continue to work because of the downloaded deployment. Also, I'm wondering, what is the point of a Lambda at the cloud, versioning and storage I assume.
I built out some IoT edge infrastructure where the lambda functions deployed to GreenGrass core only performed the forwarding to IoT Core on behalf of the non-internet capable clients (GG devices) and the heavy-lifting Lambda is still hosted on AWS. The advantage of this is your main lambda function is handling both connected and disconnected client data, so it can be aggregated for analytics, for example. Most big deployments will want to handle 100,000s of clients and you wouldn't leave systems completely offline and isolated. For your own home hobby build, you might not need the cloud parts.
Thanks for the video it helps a lot.
When i followed the same everything is working fine but from lambda to topic it returns empty payload even i gave raw data.
Can you please help me on this.
Dunno if anyone gives a shit but if you are bored like me during the covid times then you can stream all of the new series on InstaFlixxer. I've been watching with my gf for the last months :)
@Jake Zander definitely, I've been watching on InstaFlixxer for since november myself =)