Recipe format Recipe variables Recipe examples

AWS IoT Greengrass component recipe reference

The component recipe is a file that defines a component's details, dependencies, artifacts, and lifecycles. The component lifecycle specifies the commands to run to install, run, and shut down the component, for example. The AWS IoT Greengrass core uses the lifecycles that you define in the recipe to install and run components. The AWS IoT Greengrass service uses the recipe to identify the dependencies and artifacts to deploy to your core devices when you deploy the component.

In the recipe, you can define unique dependencies and lifecycles for each platform that a component supports. You can use this capability to deploy a component to devices with multiple platforms that have different requirements. You can also use this to prevent AWS IoT Greengrass from installing a component on devices that don't support it.

Each recipe contains a list of manifests. Each manifest specifies a set of platform requirements and the lifecycle and artifacts to use for core devices whose platform meets those requirements. The core device uses the first manifest with platform requirements that the device meets. Specify a manifest without any platform requirements to match any core device.

You can also specify a global lifecycle that isn't in a manifest. In the global lifecycle, you can use selection keys that identify sub-sections of the lifecycle. Then, you can specify these selection keys within a manifest to use those sections of the global lifecycle in addition to the manifest's lifecycle. The core device uses the manifest's selection keys only if the manifest doesn't define a lifecycle. You can use the all selection in a manifest to match sections of the global lifecycle without selection keys.

After the AWS IoT Greengrass Core software selects a manifest that matches the core device, it does the following to identify the lifecycle steps to use:

If the selected manifest defines a lifecycle, the core device uses that lifecycle.
If the selected manifest doesn't define a lifecycle, the core device uses the global lifecycle. The core device does the following to identify which sections of the global lifecycle to use:
- If the manifest defines selection keys, the core device uses the sections of the global lifecycle that have the manifest's selection keys.
- If the manifest doesn't define selection keys, the core device uses the sections of the global lifecycle that don't have selection keys. This behavior is equivalent to a manifest that defines the all selection.

Important

A core device must match least one manifest's platform requirements to install the component. If no manifest matches the core device, then the AWS IoT Greengrass Core software doesn't install the component and the deployment fails.

You can define recipes in JSON or YAML format. The recipe examples section includes recipes in each format.

Topics

Recipe format
Recipe variables
Recipe examples

Recipe format

When you define a recipe for a component, you specify the following information in the recipe document. The same structure applies to recipes in YAML and JSON formats.

RecipeFormatVersion

The template version for the recipe. Choose the following option:

2020-01-25

ComponentName

The name of the component that this recipe defines. The component name must be unique in your AWS account in each Region.

Tips

Use inverse domain name format to avoid name collision within your company. For example, if your company owns example.com and you work on a solar energy project, you can name your Hello World component com.example.solar.HelloWorld. This helps avoid component name collisions within your company.
Avoid the aws.greengrass prefix in your component names. AWS IoT Greengrass uses this prefix for the public components that it provides. If you choose the same name as a public component, your component replaces that component. Then, AWS IoT Greengrass provides your component instead of the public component when it deploys components with a dependency on that public component. This feature enables you to override the behavior of public components, but it can also break other components if you don't intend to override a public component.

ComponentVersion

The version of the component.

Note

AWS IoT Greengrass uses semantic versions for components. Semantic versions follow a major.minor.patch number system. For example, version 1.0.0 represents the first major release for a component. For more information, see the semantic version specification.

ComponentDescription

(Optional) The description of the component.

ComponentPublisher

The publisher or author of the component.

ComponentConfiguration

(Optional) An object that defines the configuration or parameters for the component. You define the default configuration, and then when you deploy the component, you can specify the configuration object to provide to the component. Component configuration supports nested parameters and structures. This object contains the following information:

DefaultConfiguration: An object that defines the default configuration for the component. You define the structure of this object.

Note

AWS IoT Greengrass uses JSON for configuration values. JSON specifies a number type but doesn't differentiate between integers and floats. As a result, configuration values might convert to floats in AWS IoT Greengrass. To ensure that your component uses the correct data type, we recommend that you define numeric configuration values as strings. Then, have your component parse them as integers or floats. This ensures that your configuration values have the same type in the configuration and on your core device.

ComponentDependencies

(Optional) A dictionary of objects that each define a component dependency for the component. The key for each object identifies the name of the component dependency. AWS IoT Greengrass installs component dependencies when the component installs. AWS IoT Greengrass waits for dependencies to start before it starts the component. Each object contains the following information:

VersionRequirement

The semantic version constraint that defines the component versions for this dependency. You can specify a version or a range of versions. For more information, see the npm semantic version calculator.

DependencyType

(Optional) The type of this dependency. Choose from the following options.

SOFT – The component doesn't restart if the dependency changes state.
HARD – The component restarts if the dependency changes state.

Defaults to HARD.

Manifests

A list of objects that each define the component's lifecycle, parameters, and requirements for a platform. If a core device matches multiple manifests' platform requirements, AWS IoT Greengrass uses the first manifest that the core device matches. To ensure that core devices use the correct manifest, define the manifests with stricter platform requirements first. A manifest that applies to all platforms must be the last manifest in the list.

Important

Each object contains the following information:

Name

(Optional) A friendly name for the platform that this manifest defines.

If you omit this parameter, AWS IoT Greengrass creates a name from the platform os and architecture.

Platform

(Optional) An object that defines the platform to which this manifest applies. Omit this parameter to define a manifest that applies to all platforms.

This object specifies key-value pairs about the platform on which a core device runs. When you deploy this component, the AWS IoT Greengrass Core software compares these key-value pairs with the platform attributes on the core device. The AWS IoT Greengrass Core software always defines os and architecture, and it might define additional attributes. You can specify custom platform attributes for a core device when you deploy the Greengrass nucleus component. For more information, see the platform overrides parameter of the Greengrass nucleus component.

For each key-value pair, you can specify one of the following values:

An exact value, such as linux. Exact values must start with a letter or a number.
*, which matches any value. This also matches when a value isn't present.
A Java-style regular expression, such as /windows|linux/. The regular expression must start and end with a slash character (/). For example, the regular expression /.+/ matches any non-blank value.

This object contains the following information:

os

(Optional) The name of the operating system for the platform that this manifest supports. Common platforms include the following values:

linux
darwin (macOS)

architecture

(Optional) The processor architecture for the platform that this manifest supports. Common architectures include the following values:

amd64
arm
aarch64
x86

key

(Optional) A platform attribute that you define for this manifest. Replace key with the name of the platform attribute. The AWS IoT Greengrass Core software matches this platform attribute with the key-value pairs that you specify in the Greengrass nucleus component configuration. For more information, see the platform overrides parameter of the Greengrass nucleus component.

Tip

Use inverse domain name format to avoid name collision within your company. For example, if your company owns example.com and you work on a radio project, you can name a custom platform attribute com.example.radio.RadioModule. This helps avoid platform attribute name collisions within your company.

For example, you might define a platform attribute, com.example.radio.RadioModule, to specify a different manifest based on which radio module is available on a core device. Each manifest can include different artifacts that apply to different hardware configurations, so that you deploy the minimal set of software to the core device.

Lifecycle

An object that defines how to install and run the component on the platform that this manifest defines. You can also define a global lifecycle that applies to all platforms. The core device uses the global lifecycle only if the manifest to use doesn't specify a lifecycle.

Note

You define this lifecycle within a manifest. The lifecycle steps that you specify here apply to only the platform that this manifest defines. You can also define a global lifecycle that applies to all platforms.

This object contains the following information:

Setenv

(Optional) A dictionary of environment variables to provide to all lifecycle scripts. You can override these environment variables with Setenv in each lifecycle script.

Bootstrap

(Optional) An object that defines the script to run when the AWS IoT Greengrass Core software deploys the component. This lifecycle step runs before the install lifecycle step in the following cases:

The component deploys to the core device for the first time.
The component version changes.
The bootstrap script changes as the result of a component configuration update.

You can use this lifecycle step to restart the AWS IoT Greengrass Core software or restart the core device. This lets you develop a component that performs a restart after it installs operating system updates or runtime updates, for example.

After the AWS IoT Greengrass Core software completes the bootstrap step for all components that have a bootstrap step in a deployment, the software restarts.

Important

You must configure the AWS IoT Greengrass Core software as a system service to restart the AWS IoT Greengrass Core software or the core device. If you don't configure the AWS IoT Greengrass Core software as a system service, the software won't restart. For more information, see Configure AWS IoT Greengrass as a system service.

This object contains the following information:

Script

The script to run. The exit code of this script defines the restart instruction. Use the following exit codes:

0 – Don't restart the AWS IoT Greengrass Core software or the core device. The AWS IoT Greengrass Core software still restarts after all components bootstrap.
100 – Request to restart the AWS IoT Greengrass Core software.
101 – Request to restart the core device.

Exit codes 100 to 199 are reserved for special behavior. Other exit codes represent script errors.

RequiresPrivilege

(Optional) You can run the script with root privileges. If you set this option to true, then the AWS IoT Greengrass Core software runs this lifecycle script as root instead of as the system user that you configure to run this component. Defaults to false.

Timeout

(Optional) The maximum amount of time in seconds that the script can run before the AWS IoT Greengrass Core software terminates the process.

Default: 120 seconds

Setenv

(Optional) The dictionary of environment variables to provide to the script. These environment variables override the variables that you provide in Lifecycle.Setenv.

Install

(Optional) An object that defines the script to run when the component installs. The AWS IoT Greengrass Core software also runs this lifecycle step when each time the software launches.

If the Install script exits with a success code, the component enters the INSTALLED state.

This object contains the following information:

Script

The script to run.

RequiresPrivilege

Skipif

(Optional) The check to determine whether or not to run the script. You can define to check if an executable is on the path or if a file exists. If the output is true, then the AWS IoT Greengrass Core software skips the step. Choose from the following checks:

onpath runnable – Check if a runnable is on the system path. For example, use onpath python3 to skip this lifecycle step if Python 3 is available.
exists file – Check if a file exists. For example, use exists /tmp/my-configuration.db to skip this lifecycle step if /tmp/my-configuration.db is present.

Timeout

(Optional) The maximum amount of time in seconds that the script can run before the AWS IoT Greengrass Core software terminates the process.

Default: 120 seconds

Setenv

(Optional) The dictionary of environment variables to provide to the script. These environment variables override the variables that you provide in Lifecycle.Setenv.

Run

(Optional) An object that defines the script to run when the component starts.

The component enters the RUNNING state when this lifecycle step runs. If the Run script exits with a success code, the component enters the FINISHED state.

Components that depend on this component start when this lifecycle step runs. To run a background process, such as a service that dependent components use, use the Startup lifecycle step instead.

Note

You can define only one Startup or Run lifecycle.

This object contains the following information:

Script

The script to run.

RequiresPrivilege

Skipif

onpath runnable – Check if a runnable is on the system path. For example, use onpath python3 to skip this lifecycle step if Python 3 is available.
exists file – Check if a file exists. For example, use exists /tmp/my-configuration.db to skip this lifecycle step if /tmp/my-configuration.db is present.

Timeout

(Optional) The maximum amount of time in seconds that the script can run before the AWS IoT Greengrass Core software terminates the process.

This lifecycle step doesn't timeout by default. If you omit this timeout, the Run script runs until it exits.

Setenv

(Optional) The dictionary of environment variables to provide to the script. These environment variables override the variables that you provide in Lifecycle.Setenv.

Startup

(Optional) An object that defines the background process to run when the component starts.

Use Startup to run a command that must exit successfully before dependent components can start. For example, you might define a Startup step that starts the MySQL process with /etc/init.d/mysqld start.

The component enters the STARTING state when this lifecycle step runs. If the Startup script exits with a success code, the component enters the RUNNING state. Then, dependent components can start.

Note

You can define only one Startup or Run lifecycle.

This object contains the following information:

Script

The script to run.

RequiresPrivilege

Skipif

onpath runnable – Check if a runnable is on the system path. For example, use onpath python3 to skip this lifecycle step if Python 3 is available.
exists file – Check if a file exists. For example, use exists /tmp/my-configuration.db to skip this lifecycle step if /tmp/my-configuration.db is present.

Timeout

(Optional) The maximum amount of time in seconds that the script can run before the AWS IoT Greengrass Core software terminates the process.

Default: 120 seconds

Setenv

(Optional) The dictionary of environment variables to provide to the script. These environment variables override the variables that you provide in Lifecycle.Setenv.

Shutdown

(Optional) An object that defines the script to run when the component shuts down.

If you start a background process in Startup, use the Shutdown step to stop that process when the component shuts down. For example, you might define a Shutdown step that stops the MySQL process with /etc/init.d/mysqld stop.

The component enters the STOPPING state when this lifecycle step runs.

This object contains the following information:

Script

The script to run.

RequiresPrivilege

Skipif

onpath runnable – Check if a runnable is on the system path. For example, use onpath python3 to skip this lifecycle step if Python 3 is available.
exists file – Check if a file exists. For example, use exists /tmp/my-configuration.db to skip this lifecycle step if /tmp/my-configuration.db is present.

Timeout

(Optional) The maximum amount of time in seconds that the script can run before the AWS IoT Greengrass Core software terminates the process.

Default: 15 seconds.

Setenv

(Optional) The dictionary of environment variables to provide to the script. These environment variables override the variables that you provide in Lifecycle.Setenv.

Recover

(Optional) An object that defines the script to run when the component encounters an error.

This step runs when a component enters the ERRORED state. If the component becomes ERRORED three times without successfully recovering, the component changes to the BROKEN state. To fix a BROKEN component, you must deploy it again.

This object contains the following information:

Script

The script to run.

RequiresPrivilege

Skipif

onpath runnable – Check if a runnable is on the system path. For example, use onpath python3 to skip this lifecycle step if Python 3 is available.
exists file – Check if a file exists. For example, use exists /tmp/my-configuration.db to skip this lifecycle step if /tmp/my-configuration.db is present.

Timeout

(Optional) The maximum amount of time in seconds that the script can run before the AWS IoT Greengrass Core software terminates the process.

Default: 60 seconds.

Setenv

(Optional) The dictionary of environment variables to provide to the script. These environment variables override the variables that you provide in Lifecycle.Setenv.

Selections

(Optional) A list of selection keys that specify sections of the global lifecycle to run for this manifest. In the global lifecycle, you can define lifecycle steps with selection keys at any level to select sub-sections of the lifecycle. Then, the core device uses those sections that match the selection keys in this manifest. For more information, see the global lifecycle examples.

Important

The core device uses the selections from the global lifecycle only if this manifest doesn't define a lifecycle.

You can specify the all selection key to run sections of the global lifecycle that don't have selection keys.

Artifacts

(Optional) A list of objects that each define a binary artifact for the component on the platform that this manifest defines. For example, you can define code or images as artifacts.

When the component deploys, the AWS IoT Greengrass Core software downloads the artifact to a folder on the core device. You can also define artifacts as archive files that the software extracts after it downloads them.

You can use recipe variables to get the paths to the folders where the artifacts install on the core device.

Normal files – Use the artifacts:path recipe variable to get the path to the folder that contains the artifacts. For example, specify {artifacts:path}/my_script.py in a recipe to get the path to an artifact that has the URI s3://DOC-EXAMPLE-BUCKET/path/to/my_script.py.
Extracted archives – Use the artifacts:decompressedPath recipe variable to get the path to the folder that contains the extracted archive artifacts. The AWS IoT Greengrass Core software extracts each archive to a folder with the same name as the archive. For example, specify {artifacts:decompressedPath}/my_archive/my_script.py in a recipe to get the path to my_script.py in the archive artifact that has the URI s3://DOC-EXAMPLE-BUCKET/path/to/my_artifact.zip.

Note

When you develop a component with an archive artifact on a local core device, you might not have a URI for that artifact. To test your component with an Unarchive option that extracts the artifact, specify a URI where the file name matches the name of your archive artifact file. You can specify the URI where you expect to upload the archive artifact, or you can specify a new placeholder URI. For example, to extract the my_archive.zip artifact during a local deployment, you can specify s3://DOC-EXAMPLE-BUCKET/my_archive.zip.

Each object contains the following information:

URI

The URI of an artifact in an S3 bucket. The AWS IoT Greengrass Core software fetches the artifact from this URI when the component installs, unless the artifact already exists on the device. Each artifact must have a unique file name within each manifest.

Unarchive

(Optional) The type of archive to unpack. Choose from the following options:

NONE – The file isn't an archive to unpack. The AWS IoT Greengrass Core software installs the artifact to a folder on the core device. You can use the artifacts:path recipe variable to get the path to this folder.
ZIP – The file is a ZIP archive. The AWS IoT Greengrass Core software extracts the archive to a folder with the same name as the archive. You can use the artifacts:decompressedPath recipe variable to get the path to the folder that contains this folder.

Defaults to NONE.

Permission

(Optional) An object that defines the access permissions to set for this artifact file. You can set the read permission and the execute permission.

Note

You can't set the write permission, because the AWS IoT Greengrass Core software doesn't allow components to edit artifact files in the artifacts folder. To edit an artifact file in a component, copy it to another location or publish and deploy a new artifact file.

If you define an artifact as an archive to unpack, then the AWS IoT Greengrass Core software sets these access permissions on the files that it unpacks from the archive. The AWS IoT Greengrass Core software sets the folder's access permissions to ALL for Read and Execute. This allows components to view the unpacked files in the folder. To set permissions on individual files from the archive, you can set the permissions in the install lifecycle script.

This object contains the following information:

Read

(Optional) The read permission to set for this artifact file. To allow other components to access this artifact, such as components that depend on this component, specify ALL. Choose from the following options:

NONE – The file isn't readable.
OWNER – The file is readable by the system user that you configure to run this component.
ALL – The file is readable by all users.

Defaults to OWNER.

Execute

(Optional) The run permission to set for this artifact file. The Execute permission implies the Read permission. For example, if you specify ALL for Execute, then all users can read and run this artifact file.

Choose from the following options:

NONE – The file isn't runnable.
OWNER – The file is runnable by the system user that you configure to run the component.
ALL – The file is runnable by all users.

Defaults to NONE.

Lifecycle

An object that defines how to install and run the component. The core device uses the global lifecycle only if the manifest to use doesn't specify a lifecycle.

Note

You define this lifecycle outside a manifest. You can also define a manifest lifecycle that applies to the platforms that match that manifest.

In the global lifecycle, you can specify lifecycles that run for certain selection keys that you specify in each manifest. Selection keys are strings that identify sections of the global lifecycle to run for each manifest.

The all selection key is the default on any section without a selection key. This means that you can specify the all selection key in a manifest to run the sections of the global lifecycle without selection keys. You don't need to specify the all selection key in the global lifecycle.

If a manifest doesn't define a lifecycle or selection keys, the core device defaults to use the all selection. This means that in this case, the core device uses the sections of the global lifecycle that don't use selection keys.

This object contains the same information as the manifest lifecycle, but you can specify selection keys at any level to select sub-sections of the lifecycle.

Tip

We recommend that you use only lowercase letters for each selection key to avoid conflicts between selection keys and lifecycle keys. Lifecycle keys start with a capital letter.

Example global lifecycle with top-level selection keys


Lifecycle:
  key1:
    Install:
      Skipif: onpath executable | exists file
      Script: command1
  key2:
    Install:
      Script: command2
  all:
    Install:
      Script: command3

Example global lifecycle with bottom-level selection keys


Lifecycle:
  Install:
    Script:
      key1: command1
      key2: command2
      all: command3

Example global lifecycle with multiple levels of selection keys


Lifecycle:
  key1:
    Install:
      Skipif: onpath executable | exists file
      Script: command1
  key2:
    Install:
      Script: command2
  all:
    Install:
      Script:
        key3: command3
        key4: command4
        all: command5

Recipe variables

Recipe variables expose information from the current component and nucleus for you to use in your recipes. For example, you can use recipe variables to pass component configuration parameters to a lifecycle script that exists as an artifact.

Recipe variables use {recipe_variable} syntax. The double curly braces indicate a recipe variable.

AWS IoT Greengrass supports the following recipe variables:

component_dependency_name:configuration:json_pointer

The value of a configuration parameter for the component that this recipe defines or for a component on which this component depends.

You can use this variable to provide a parameter to a script that you run in the component lifecycle.

This recipe variable has the following inputs:

component_dependency_name – (Optional) The name of the component dependency to query. Omit this segment to query the component that this recipe defines. You can specify only direct dependencies.
json_pointer – The JSON pointer to the configuration value to evaluate. JSON pointers start with a forward slash /. To identify a value in a nested component configuration, use forward slashes (/) to separate the keys for each level in the configuration. You can use a number as a key to specify an index in a list. For more information, see the JSON pointer specification.

AWS IoT Greengrass Core uses JSON pointers for recipes in YAML format.

The JSON pointer can reference the following node types:

A value node. AWS IoT Greengrass Core replaces the recipe variable with the string representation of the value. Null values convert to null as a string.
An object node. AWS IoT Greengrass Core replaces the recipe variable with the serialized JSON string representation of that object.
No node. AWS IoT Greengrass Core doesn't replace the recipe variable.

For example, the {configuration:/Message} recipe variable retrieves the value of the Message key in the component configuration. The {com.example.MyComponentDependency:configuration:/server/port} recipe variable retrieves the value of port in the server configuration object of a component dependency.

component_dependency_name:artifacts:path

The root path of the artifacts for the component that this recipe defines or for a component on which this component depends.

When a component installs, AWS IoT Greengrass copies the component's artifacts to the folder that this variable exposes. You can use this variable to identify the location of a script to run in the component lifecycle, for example.

The folder at this path is read-only. To modify artifact files, copy the files to another location, such as the current working directory ($PWD or .). Then, modify the files there.

To read or run an artifact from a component dependency, that artifact's Read or Execute permission must be ALL. For more information, see the artifact permissions that you define in the component recipe.

This recipe variable has the following inputs:

component_dependency_name – (Optional) The name of the component dependency to query. Omit this segment to query the component that this recipe defines. You can specify only direct dependencies.

component_dependency_name:artifacts:decompressedPath

The root path of the decompressed archive artifacts for the component that this recipe defines or for a component on which this component depends.

When a component installs, AWS IoT Greengrass unpacks the component's archive artifacts to the folder that this variable exposes. You can use this variable to identify the location of a script to run in the component lifecycle, for example.

Each artifact unzips to a folder within the decompressed path, where the folder has the same name as the artifact minus its extension. For example, a ZIP artifact named models.zip unpacks to the {artifacts:decompressedPath}/models folder.

The folder at this path is read-only. To modify artifact files, copy the files to another location, such as the current working directory ($PWD or .). Then, modify the files there.

This recipe variable has the following inputs:

component_dependency_name – (Optional) The name of the component dependency to query. Omit this segment to query the component that this recipe defines. You can specify only direct dependencies.

component_dependency_name:work:path

The work path for the component that this recipe defines or for a component on which this component depends. The value of this recipe variable is equivalent to the output of the $PWD environment variable and the pwd command when run from the context of the component.

You can use this recipe variable to share files between a component and a dependency.

The folder at this path is readable and writable by the component that this recipe defines and by other components that run as the same user and group.

This recipe variable has the following inputs:

component_dependency_name – (Optional) The name of the component dependency to query. Omit this segment to query the component that this recipe defines. You can specify only direct dependencies.

kernel:rootPath

The AWS IoT Greengrass Core root path.

Recipe examples

You can reference the following recipe examples to help you create recipes for your components.

Topics

Hello World component recipe
Python runtime component example
Component recipe that specifies several fields

Hello World component recipe

The following recipe describes a Hello World component that runs a Python script. This component supports Linux and accepts a Message parameter that AWS IoT Greengrass passes as an argument to the Python script. This is the recipe for the Hello World component in the Getting started tutorial.

Python runtime component example

The following recipe describes a component that installs Python. This component supports 64-bit Linux devices.

Component recipe that specifies several fields

The following component recipe uses several recipe fields.

JSON


{
  "RecipeFormatVersion": "2020-01-25",
  "ComponentName": "com.example.FooService",
  "ComponentDescription": "Complete recipe for AWS IoT Greengrass components",
  "ComponentPublisher": "Amazon",
  "ComponentVersion": "1.0.0",
  "ComponentConfiguration": {
    "DefaultConfiguration": {
      "TestParam": "TestValue"
    }
  },
  "ComponentDependencies": {
    "BarService": {
      "VersionRequirement": "^1.1.0",
      "DependencyType": "SOFT"
    },
    "BazService": {
      "VersionRequirement": "^2.0.0"
    }
  },
  "Manifests": [
    {
      "Platform": {
        "os": "linux",
        "architecture": "amd64"
      },
      "Lifecycle": {
        "Install": {
          "Skipif": "onpath git",
          "Script": "sudo apt-get install git"
        }
      },
      "Artifacts": [
        {
          "URI": "s3://DOC-EXAMPLE-BUCKET/hello_world.zip",
          "Unarchive": "ZIP"
        },
        {
          "URI": "s3//DOC-EXAMPLE-BUCKET/hello-world2.py"
        }
      ]
    },
    {
      "Lifecycle": {
        "Start": {
          "Skipif": "onpath git",
          "Script": "sudo apt-get install git"
        }
      },
      "Artifacts": [
        {
          "URI": "s3://DOC-EXAMPLE-BUCKET/hello_world.py"
        }
      ]
    }
  ]
}

YAML


---
RecipeFormatVersion: 2020-01-25
ComponentName: com.example.FooService
ComponentDescription: Complete recipe for AWS IoT Greengrass components
ComponentPublisher: Amazon
ComponentVersion: '1.0.0'
ComponentConfiguration:
  DefaultConfiguration:
    TestParam: TestValue
ComponentDependencies:
  BarService:
    VersionRequirement: ^1.1.0
    DependencyType: SOFT
  BazService: VersionRequirement: ^2.0.0
Manifests:
  - Platform:
      os: linux
      architecture: amd64
    Lifecycle:
      Install:
        Skipif: onpath git
        Script: sudo apt-get install git
    Artifacts:
      - URI: s3://DOC-EXAMPLE-BUCKET/hello_world.zip
        Unarchive: ZIP
      - URI: s3//DOC-EXAMPLE-BUCKET/hello-world2.py
  - Lifecycle:
      Install:
        Skipif: onpath git
        Script: sudo apt-get install git
    Artifacts:
      - URI: s3://DOC-EXAMPLE-BUCKET/hello_world.py

Warning Javascript is disabled or is unavailable in your browser.

To use the AWS Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions.

Document Conventions

Run a Docker container

Environment variables