Creating and deploying remotely

Up until now, you have been interacting with your IoT Greengrass solution directly on the hub device using the IoT Greengrass command-line interface (CLI). Going forward, you will learn how to interact with your IoT Greengrass device from your C2 system (laptop or workstation) through the use of the AWS cloud. The CLI and local development lifecycle are great for learning the basics of IoT Greengrass and rapid iteration on component development. The best practice for production solutions is not to deploy the Greengrass CLI component to your devices and install new components locally, so next, you will learn how to package your components, store them in AWS, and complete remote deployments to your hub device.

Loading resources from the cloud

Components can include any number of artifacts defined by the recipe file, and those artifacts must be stored somewhere the Greengrass device can access them. Artifacts can be static resources of any kind:...