The token to be used for the next set of paginated results.

The maximum number of results to be returned per paginated request.

The ARN of the component version.

The token for the next set of results, or null if there are no additional results.

A list of versions that exist for the component.

The response's http status code.

The ID of the deployment.

The ARN of the target IoT thing or thing group.

The components to deploy. This is a dictionary, where each key is the name of a component, and each key's value is the version and configuration to deploy for that component.

The ID of the deployment.

The ID of the IoT job that applies the deployment to target devices.

The ARN of the IoT job that applies the deployment to target devices.

The deployment policies for the deployment. These policies define how the deployment updates components and handles failure.

The time at which the deployment was created, expressed in ISO 8601 format.

The job configuration for the deployment configuration. The job configuration specifies the rollout, timeout, and stop configurations for the deployment configuration.

The status of the deployment.

Whether or not the deployment is the latest revision for its target.

The revision number of the deployment.

The name of the deployment.

A list of key-value pairs that contain metadata for the resource. For more information, see Tag your resources in the IoT Greengrass V2 Developer Guide.

The response's http status code.

The ARN of the component version.

The platforms that the component version supports.

The status of the component version in IoT Greengrass V2. This status is different from the status of the component on a core device.

The ARN of the component version.

The version of the component.

The time at which the component was created, expressed in ISO 8601 format.

The name of the component.

The publisher of the component version.

The description of the component version.

A list of key-value pairs that contain metadata for the resource. For more information, see Tag your resources in the IoT Greengrass V2 Developer Guide.

The response's http status code.

The name of the core device. This is also the name of the IoT thing.

The ARN of the resource.

A list of key-value pairs that contain metadata for the resource. For more information, see Tag your resources in the IoT Greengrass V2 Developer Guide.

The response's http status code.

The name of the core device. This is also the name of the IoT thing.

The status of the core device. The core device status can be:

• HEALTHY – The IoT Greengrass Core software and all components run on the core device without issue.
• UNHEALTHY – The IoT Greengrass Core software or a component is in a failed state on the core device.

The operating system platform that the core device runs.

The computer architecture of the core device.

The name of the core device. This is also the name of the IoT thing.

A list of key-value pairs that contain metadata for the resource. For more information, see Tag your resources in the IoT Greengrass V2 Developer Guide.

The version of the IoT Greengrass Core software that the core device runs. This version is equivalent to the version of the Greengrass nucleus component that runs on the core device. For more information, see the Greengrass nucleus component in the IoT Greengrass V2 Developer Guide.

The time at which the core device's status last updated, expressed in ISO 8601 format.

The response's http status code.

The ARN of the component version. Specify the ARN of a public component version.

The name of the artifact.

You can use the GetComponent operation to download the component recipe, which includes the URI of the artifact. The artifact name is the section of the URI after the scheme. For example, in the artifact URI greengrass:SomeArtifact.zip, the artifact name is SomeArtifact.zip.

The response's http status code.

The URL of the artifact.

The components to deploy. This is a dictionary, where each key is the name of a component, and each key's value is the version and configuration to deploy for that component.

A unique, case-sensitive identifier that you can provide to ensure that the request is idempotent. Idempotency means that the request is successfully processed only once, even if you send the request multiple times. When a request succeeds, and you specify the same client token for subsequent successful requests, the IoT Greengrass V2 service returns the successful response that it caches from the previous request. IoT Greengrass V2 caches successful responses for idempotent requests for up to 8 hours.

The deployment policies for the deployment. These policies define how the deployment updates components and handles failure.

The job configuration for the deployment configuration. The job configuration specifies the rollout, timeout, and stop configurations for the deployment configuration.

The name of the deployment.

A list of key-value pairs that contain metadata for the resource. For more information, see Tag your resources in the IoT Greengrass V2 Developer Guide.

The ARN of the target IoT thing or thing group.

The ID of the deployment.

The ID of the IoT job that applies the deployment to target devices.

The ARN of the IoT job that applies the deployment to target devices.

The response's http status code.

The list of client devices to associate.

The name of the core device. This is also the name of the IoT thing.

The list of any errors for the entries in the request. Each error entry contains the name of the IoT thing that failed to associate.

The response's http status code.

The token to be used for the next set of paginated results.

The maximum number of results to be returned per paginated request.

The name of the core device. This is also the name of the IoT thing.

A list that summarizes each component on the core device.

The token for the next set of results, or null if there are no additional results.

The response's http status code.

The ID of the deployment.

A message that communicates if the cancel was successful.

The response's http status code.

The list of client devices to disassociate.

The name of the core device. This is also the name of the IoT thing.

The list of errors (if any) for the entries in the request. Each error entry contains the name of the IoT thing that failed to disassociate.

The response's http status code.

The core device status by which to filter. If you specify this parameter, the list includes only core devices that have this status. Choose one of the following options:

• HEALTHY – The IoT Greengrass Core software and all components run on the core device without issue.
• UNHEALTHY – The IoT Greengrass Core software or a component is in a failed state on the core device.

The ARN of the IoT thing group by which to filter. If you specify this parameter, the list includes only core devices that are members of this thing group.

The token to be used for the next set of paginated results.

The maximum number of results to be returned per paginated request.

The token for the next set of results, or null if there are no additional results.

A list that summarizes each core device.

The response's http status code.

The platform to use to resolve compatible components.

The list of components to resolve.

A list of components that meet the requirements that you specify in the request. This list includes each component's recipe that you can use to install the component.

The response's http status code.

The token to be used for the next set of paginated results.

The maximum number of results to be returned per paginated request.

The name of the core device. This is also the name of the IoT thing.

The token for the next set of results, or null if there are no additional results.

A list that summarizes each deployment on the core device.

The response's http status code.

The ARN of the target IoT thing or thing group.

The token to be used for the next set of paginated results.

The filter for the list of deployments. Choose one of the following options:

• ALL – The list includes all deployments.
• LATEST_ONLY – The list includes only the latest revision of each deployment.

Default: LATEST_ONLY

The maximum number of results to be returned per paginated request.

The token for the next set of results, or null if there are no additional results.

A list that summarizes each deployment.

The response's http status code.

The ARN of the resource to tag.

A list of key-value pairs that contain metadata for the resource. For more information, see Tag your resources in the IoT Greengrass V2 Developer Guide.

The response's http status code.

The ARN of the resource to untag.

A list of keys for tags to remove from the resource.

The response's http status code.

The token to be used for the next set of paginated results.

The scope of the components to list.

Default: PRIVATE

The maximum number of results to be returned per paginated request.

A list that summarizes each component.

The token for the next set of results, or null if there are no additional results.

The response's http status code.

The ARN of the component version.

A unique, case-sensitive identifier that you can provide to ensure that the request is idempotent. Idempotency means that the request is successfully processed only once, even if you send the request multiple times. When a request succeeds, and you specify the same client token for subsequent successful requests, the IoT Greengrass V2 service returns the successful response that it caches from the previous request. IoT Greengrass V2 caches successful responses for idempotent requests for up to 8 hours.

The recipe to use to create the component. The recipe defines the component's metadata, parameters, dependencies, lifecycle, artifacts, and platform compatibility.

You must specify either inlineRecipe or lambdaFunction.-- -- Note: This Lens automatically encodes and decodes Base64 data. -- The underlying isomorphism will encode to Base64 representation during -- serialisation, and decode from Base64 representation during deserialisation. -- This Lens accepts and returns only raw unencoded data.

The parameters to create a component from a Lambda function.

You must specify either inlineRecipe or lambdaFunction.

A list of key-value pairs that contain metadata for the resource. For more information, see Tag your resources in the IoT Greengrass V2 Developer Guide.

The ARN of the component version.

The response's http status code.

The name of the component.

The version of the component.

The time at which the component was created, expressed in ISO 8601 format.

The status of the component version in IoT Greengrass V2. This status is different from the status of the component on a core device.

The format of the recipe.

The ARN of the component version.

A list of key-value pairs that contain metadata for the resource. For more information, see Tag your resources in the IoT Greengrass V2 Developer Guide.

The response's http status code.

The format of the recipe.

The recipe of the component version.-- -- Note: This Lens automatically encodes and decodes Base64 data. -- The underlying isomorphism will encode to Base64 representation during -- serialisation, and decode from Base64 representation during deserialisation. -- This Lens accepts and returns only raw unencoded data.

The token to be used for the next set of paginated results.

The maximum number of results to be returned per paginated request.

The name of the core device. This is also the name of the IoT thing.

A list that describes the client devices that are associated with the core device.

The token for the next set of results, or null if there are no additional results.

The response's http status code.

The name of the IoT thing that represents the client device to associate.

The error code for the request.

A message that provides additional information about the error.

The name of the IoT thing whose associate request failed.

The time that the client device was associated, expressed in ISO 8601 format.

The name of the IoT thing that represents the associated client device.

The state of the component.

A message that communicates details, such as errors, about the status of the component.

A dictionary of errors that communicate why the component is in an error state. For example, if IoT Greengrass can't access an artifact for the component, then errors contains the artifact's URI as a key, and the error message as the value for that key.

The ARN of the component version.

The name of the component.

The latest version of the component and its details.

The version of the component.

The version requirements for the component's dependencies. Greengrass core devices get the version requirements from component recipes.

IoT Greengrass V2 uses semantic version constraints. For more information, see Semantic Versioning.

The name of the component.

The list of configuration nodes to reset to default values on target devices. Use JSON pointers to specify each node to reset. JSON pointers start with a forward slash (/) and use forward slashes to separate the key for each level in the object. For more information, see the JSON pointer specification and Reset configuration updates in the IoT Greengrass V2 Developer Guide.

A serialized JSON string that contains the configuration object to merge to target devices. The core device merges this configuration with the component's existing configuration. If this is the first time a component deploys on a device, the core device merges this configuration with the component's default configuration. This means that the core device keeps it's existing configuration for keys and values that you don't specify in this object. For more information, see Merge configuration updates in the IoT Greengrass V2 Developer Guide.

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.

Default: HARD

The component version requirement for the component dependency.

IoT Greengrass V2 uses semantic version constraints. For more information, see Semantic Versioning.

The version of the component.

The system user and group that the IoT Greengrass Core software uses to run component processes on the core device. If you omit this parameter, the IoT Greengrass Core software uses the system user and group that you configure for the core device. For more information, see Configure the user and group that run components in the IoT Greengrass V2 Developer Guide.

The configuration updates to deploy for the component. You can define reset updates and merge updates. A reset updates the keys that you specify to the default configuration for the component. A merge updates the core device's component configuration with the keys and values that you specify. The IoT Greengrass Core software applies reset updates before it applies merge updates. For more information, see Update component configurations in the IoT Greengrass V2 Developer Guide.

The platforms that the component version supports.

The ARN of the component version.

The version of the component.

The time at which the component was created, expressed in ISO 8601 format.

The publisher of the component version.

The description of the component version.

The friendly name of the platform. This name helps you identify the platform.

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

A dictionary of attributes for the platform. The IoT Greengrass Core software defines the os and platform by default. You can specify additional platform attributes for a core device when you deploy the Greengrass nucleus component. For more information, see the Greengrass nucleus component in the IoT Greengrass V2 Developer Guide.

The POSIX system user and (optional) group to use to run this component. Specify the user and group separated by a colon (:) in the following format: user:group. The group is optional. If you don't specify a group, the IoT Greengrass Core software uses the primary user for the group.

If you omit this parameter, the IoT Greengrass Core software uses the default system user and group that you configure on the Greengrass nucleus component. For more information, see Configure the user and group that run components.

The system resource limits to apply to this component's process on the core device.

If you omit this parameter, the IoT Greengrass Core software uses the default system resource limits that you configure on the Greengrass nucleus component. For more information, see Configure system resource limits for components.

The ARN of the component version.

The version of the component.

The name of the component.

The status of the core device. Core devices can have the following statuses:

• HEALTHY – The IoT Greengrass Core software and all components run on the core device without issue.
• UNHEALTHY – The IoT Greengrass Core software or a component is in a failed state on the core device.

The name of the core device. This is also the name of the IoT thing.

The time at which the core device's status last updated, expressed in ISO 8601 format.

The ARN of the target IoT thing or thing group.

The ID of the deployment.

The time at which the deployment was created, expressed in ISO 8601 format.

The status of the deployment.

Whether or not the deployment is the latest revision for its target.

The revision number of the deployment.

The name of the deployment.

Whether or not to notify components and wait for components to become safe to update. Choose from the following options:

• NOTIFY_COMPONENTS – The deployment notifies each component before it stops and updates that component. Components can use the SubscribeToComponentUpdates IPC operation to receive these notifications. Then, components can respond with the DeferComponentUpdate IPC operation. For more information, see Create deployments in the IoT Greengrass V2 Developer Guide.
• SKIP_NOTIFY_COMPONENTS – The deployment doesn't notify components or wait for them to be safe to update.

Default: NOTIFY_COMPONENTS

The amount of time in seconds that each component on a device has to report that it's safe to update. If the component waits for longer than this timeout, then the deployment proceeds on the device.

Default: 60

The amount of time in seconds that a component can validate its configuration updates. If the validation time exceeds this timeout, then the deployment proceeds for the device.

Default: 30

The rollout configuration for the job. This configuration defines the rate at which the job rolls out to the fleet of target devices.

The stop configuration for the job. This configuration defines when and how to stop a job rollout.

The timeout configuration for the job. This configuration defines the amount of time each device has to complete the job.

The failure handling policy for the configuration deployment. This policy defines what to do if the deployment fails.

Default: ROLLBACK

The configuration validation policy for the configuration deployment. This policy defines how long each component has to validate its configure updates.

The component update policy for the configuration deployment. This policy defines when it's safe to deploy the configuration to devices.

The name of the IoT thing that represents the client device to disassociate.

The error code for the request.

A message that provides additional information about the error.

The name of the IoT thing whose disassociate request failed.

The ID of the IoT job that applies the deployment to target devices.

The ARN of the IoT job that applies the deployment to target devices.

The reason code for the update, if the job was updated.

The description of the deployment job.

The ID of the deployment.

The name of the deployment.

The ARN of the target IoT thing or thing group.

The status of the deployment job on the Greengrass core device.

The time at which the deployment was created, expressed in ISO 8601 format.

The time at which the deployment job was last modified, expressed in ISO 8601 format.

Whether or not the component is a root component.

The version of the component.

The name of the component.

The details about the lifecycle state of the component.

The lifecycle state of the component.

The list of criteria that define when and how to cancel the configuration deployment.

The type of job deployment failure that can cancel a job.

The action to perform when the criteria are met.

The minimum percentage of failureType failures that occur before the job can cancel.

This parameter supports up to two digits after the decimal (for example, you can specify 10.9 or 10.99, but not 10.999).

The minimum number of things that receive the configuration before the job can cancel.

The exponential rate to increase the job rollout rate.

The maximum number of devices that receive a pending job notification, per minute.

The minimum number of devices that receive a pending job notification, per minute, when the job starts. This parameter defines the initial rollout rate of the job.

The exponential factor to increase the rollout rate for the job.

This parameter supports up to one digit after the decimal (for example, you can specify 1.5, but not 1.55).

The criteria to increase the rollout rate for the job.

The number of devices to receive the job notification before the rollout rate increases.

The number of devices to successfully run the configuration job before the rollout rate increases.

The amount of time, in minutes, that devices have to complete the job. The timer starts when the job status is set to IN_PROGRESS. If the job status doesn't change to a terminal state before the time expires, then the job status is set to TIMED_OUT.

The timeout interval must be between 1 minute and 7 days (10080 minutes).

Whether or not the container can read information from the device's /sys folder.

Default: false

The memory size of the container, expressed in kilobytes.

Default: 16384 (16 MB)

The list of system devices that the container can access.

The list of volumes that the container can access.

Whether or not to add the component's system user as an owner of the device.

Default: false

The permission to access the device: read/only (ro) or read/write (rw).

Default: ro

The mount path for the device in the file system.

The topic to which to subscribe to receive event messages.

The type of event source. Choose from the following options:

• PUB_SUB – Subscribe to local publish/subscribe messages. This event source type doesn't support MQTT wildcards (+ and #) in the event source topic.
• IOT_CORE – Subscribe to Amazon Web Services IoT Core MQTT messages. This event source type supports MQTT wildcards (+ and #) in the event source topic.

The list of arguments to pass to the Lambda function when it runs.

The maximum size of the message queue for the Lambda function component. The IoT Greengrass core stores messages in a FIFO (first-in-first-out) queue until it can run the Lambda function to consume each message.

Whether or not the Lambda function is pinned, or long-lived.

• A pinned Lambda function starts when IoT Greengrass starts and keeps running in its own container.
• A non-pinned Lambda function starts only when it receives a work item and exists after it idles for maxIdleTimeInSeconds. If the function has multiple work items, the IoT Greengrass Core software creates multiple instances of the function.

Default: true

The encoding type that the Lambda function supports.

Default: json

The maximum amount of time in seconds that a non-pinned Lambda function can idle before the IoT Greengrass Core software stops its process.

The maximum amount of time in seconds that the Lambda function can process a work item.

The list of event sources to which to subscribe to receive work messages. The Lambda function runs when it receives a message from an event source. You can subscribe this function to local publish/subscribe messages and Amazon Web Services IoT Core MQTT messages.

The maximum number of instances that a non-pinned Lambda function can run at the same time.

The map of environment variables that are available to the Lambda function when it runs.

The interval in seconds at which a pinned (also known as long-lived) Lambda function component sends status updates to the Lambda manager component.

The parameters for the Linux process that contains the Lambda function.

The system and runtime parameters for the Lambda function as it runs on the Greengrass core device.

The version of the component.

Defaults to the version of the Lambda function as a semantic version. For example, if your function version is 3, the component version becomes 3.0.0.

The name of the component.

Defaults to the name of the Lambda function.

The platforms that the component version supports.

The component versions on which this Lambda function component depends.

The ARN of the Lambda function. The ARN must include the version of the function to import. You can't use version aliases like $LATEST.

The parameters for the container in which the Lambda function runs.

The isolation mode for the process that contains the Lambda function. The process can run in an isolated runtime environment inside the IoT Greengrass container, or as a regular process outside any container.

Default: GreengrassContainer

Whether or not to add the IoT Greengrass user group as an owner of the volume.

Default: false

The permission to access the volume: read/only (ro) or read/write (rw).

Default: ro

The path to the physical volume in the file system.

The path to the logical volume in the file system.

The ARN of the component version.

The version of the component.

The recipe of the component version.-- -- Note: This Lens automatically encodes and decodes Base64 data. -- The underlying isomorphism will encode to Base64 representation during -- serialisation, and decode from Base64 representation during deserialisation. -- This Lens accepts and returns only raw unencoded data.

The name of the component.

The maximum amount of RAM, expressed in kilobytes, that a component's processes can use on the core device.

The maximum amount of CPU time that a component's processes can use on the core device. A core device's total CPU time is equivalent to the device's number of CPU cores. For example, on a core device with 4 CPU cores, you can set this value to 2 to limit the component's processes to 50 percent usage of each CPU core. On a device with 1 CPU core, you can set this value to 0.25 to limit the component's processes to 25 percent usage of the CPU. If you set this value to a number greater than the number of CPU cores, the IoT Greengrass Core software doesn't limit the component's CPU usage.