AWS Greengrass
Developer Guide

Deploying Cloud Configurations to an AWS Greengrass Core Device

Make sure that your AWS Greengrass core device is connected to the internet (for example, see if you can successfully navigate to a web page). Next, check that the AWS Greengrass daemon has been started by running the following command on your AWS Greengrass core device:

ps aux | grep -E 'greengrass.*daemon'

If the AWS Greengrass daemon is running, you will see a root entry containing a path to the AWS Greengrass daemon, as in /greengrass/ggc/packages/x.x.x/bin/daemon. Otherwise, you can start the daemon on your device by running the following commands:

cd /greengrass/ggc/packages/x.x.x/ sudo ./greengrassd start

Next, deploy the Lambda function and subscription configurations onto your AWS Greengrass core device as follows:

On the group configuration page, choose Deployments. Under Actions, choose Deploy.

                    Screenshot of the Group page with Deployments, Actions menu, and Deploy

Choose Automatic detection.

                    Screenshot of Configure how Devices discover your Core with Automatic
                        detection highlighted.

If prompted, choose Grant permission on the Grant permission to access other services page. This creates the Greengrass service role, which allows AWS Greengrass to access other AWS services and is required for deployments to succeed. You need to do this only once per account.

The first deployment might take a few minutes. When the deployment is complete, you should see Successfully completed in the Status column on the Deployments page:

                    Screenshot showing a status of Successfully completed .