AWS Greengrass
Developer Guide

Deploy Cloud Configurations to an AWS Greengrass Core Device

  1. 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).

  2. Make sure that the AWS Greengrass daemon is running on your core device. Run the following commands in your core device terminal.

    1. To check whether the daemon is running:

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

      If the output contains a root entry for /greengrass/ggc/packages/1.6.0/bin/daemon, then the daemon is running.

    2. To start the daemon:

      cd /greengrass/ggc/core/ sudo ./greengrassd start

    Now you're ready to deploy the Lambda function and subscription configurations to your AWS Greengrass core device.

  3. In the AWS IoT console, on the group configuration page, from the Actions menu, choose Deploy.

                    Screenshot of the Group page with Deployments, Actions menu, and Deploy
  4. On the Configure how devices discover your core page, choose Automatic detection. This enables devices to automatically acquire connectivity information for the core, such as IP address, DNS, and port number. Automatic detection is recommended, but AWS Greengrass also supports manually specified endpoints. You're only prompted for the discovery method the first time that the group is deployed.

                    Screenshot of Configure how Devices discover your Core with Automatic
                        detection highlighted.
  5. 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 on your behalf. This role 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.

For help troubleshooting any issues that you encounter, see Troubleshooting AWS Greengrass Applications.