Very good explanation. 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?
This is a great video. But a little comment. The talk is targeted more to cloud engineers who want to go the IoT route and deal more with physical devices. I'm an embedded software engineer and having trouble understanding some terms like Lambda Functions, why are there such a thing, etc.
This link docs.aws.amazon.com/general/latest/gr/aws_service_limits.html says there is a limit of 200 IoT devices to a Greengrass group. That does not seem a very high number if this is to be potentially used by 1,000s of vehicles in a "Connected" fleet. How can this be scaled without creating a huge manual overhead.
Such a good explanation. Thank You!
Explained Very Well 👍
Very good explanation.
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?
Great question. @AmazonWebServices? 👀
Im digging the grass metaphor bros, catching mad vibes off of it rn
I would like to know how to enable/disable the IoT device using API ? From AWS documents, I could not find one. Please help me.
very well explained! Thank you very much.
This is a very well explained video and with a lot of detailed explanation of this all works.
This is a great video. But a little comment.
The talk is targeted more to cloud engineers who want to go the IoT route and deal more with physical devices.
I'm an embedded software engineer and having trouble understanding some terms like Lambda Functions, why are there such a thing, etc.
This link docs.aws.amazon.com/general/latest/gr/aws_service_limits.html says there is a limit of 200 IoT devices to a Greengrass group. That does not seem a very high number if this is to be potentially used by 1,000s of vehicles in a "Connected" fleet. How can this be scaled without creating a huge manual overhead.
very nicely explained a big concept. Thanks
learned Alot here..
When the internet gets disconnected , there will be no communication between the edgedevice and the cloud.
pay me pay me please