What's new in AWS IoT Greengrass Version 2 - AWS IoT Greengrass

What's new in AWS IoT Greengrass Version 2

AWS IoT Greengrass Version 2 is a new major version release of AWS IoT Greengrass. The Version 2 release introduces the following features:

Open source edge runtime

The edge runtime is now open source and distributed under the Apache 2.0 license and available on GitHub. You can now view the AWS IoT Greengrass edge runtime code, which allows you to troubleshoot interactions with your application and helps you build more reliable and performant applications running on AWS IoT Greengrass. You can also customize and extend the AWS IoT Greengrass edge runtime to meet your specific hardware and software needs. For more information, see Open source AWS IoT Greengrass client software.

Improved modularity

You can add or remove pre-built software components based on your use cases, and your device CPU and memory resources. For example, you can choose to include only pre-built AWS IoT Greengrass components, such as stream manager, when you need to process data streams with your application. Or, you can include only machine learning components when you want to perform machine learning inference locally on your devices. For more information, see Manage AWS IoT Greengrass components and AWS-provided components.

New local development tools

AWS IoT Greengrass includes a new command line interface (CLI) that enables you to locally develop and debug applications on your device. In addition, the new local debug console helps you visually debug applications on your device. With these new capabilities, you can develop and debug code on a test device before using the cloud to deploy to your production devices. For more information, see Greengrass CLI and Local debug console.

Improved fleet deployment features

AWS IoT Greengrass is now integrated with AWS IoT thing groups. This enables you to organize your devices in groups and manage application deployments across your devices with features that control rollout rates, timeouts, and rollbacks. For more information, see Deploy AWS IoT Greengrass components to devices.

AWS IoT Greengrass V2 release notes

AWS IoT Greengrass release notes provide details about AWS IoT Greengrass releases—new features, updates and improvements, and general fixes. AWS IoT Greengrass has the following types of releases:

  • New feature releases for AWS IoT Greengrass

  • AWS IoT Greengrass Core software updates

This section contains all of the AWS IoT Greengrass V2 release notes, latest first, and includes major feature changes and significant bug fixes. For information about additional minor fixes, see the aws-greengrass organization on GitHub.

Release: AWS IoT Greengrass Core software update on March 09, 2021

This release provides version 2.0.5 of the Greengrass nucleus component. It fixes an issue with network proxy support and an issue with the Greengrass data plane endpoint in AWS China Regions.

Release date: March 09, 2021

Public component changes

Important

When you deploy a component, AWS IoT Greengrass installs the latest supported versions of all component dependencies for that component. Because of this, new patch versions of AWS-provided public components might be automatically deployed to your core devices if you add new devices to a thing group, or you update the deployment that targets those devices. Some automatic updates, such as a nucleus update, can cause your devices to restart unexpectedly.

To prevent unintended updates for a component that is running on your device, we recommend that you directly include your preferred version of that component when you create a deployment. For more information about update behavior for AWS IoT Greengrass Core software, see Update the AWS IoT Greengrass Core software (OTA).

Component Details
Greengrass nucleus

Version 2.0.5 of the Greengrass nucleus is available.

Bug fixes and improvements
  • Correctly route traffic through a configured network proxy when downloading AWS-provided components.

  • Use the correct Greengrass data plane endpoint in AWS China Regions.

Release: AWS IoT Greengrass Core software update on February 04, 2021

This release provides version 2.0.4 of the Greengrass nucleus component. It includes the new greengrassDataPlanePort parameter to configure HTTPS communication over port 443 and fixes bugs. The minimal IAM policy now requires the iam:GetPolicy and sts:GetCallerIdentity when the AWS IoT Greengrass Core software installer is run with --provision true.

Release date: February 04, 2021

Public component changes

Important

When you deploy a component, AWS IoT Greengrass installs the latest supported versions of all component dependencies for that component. Because of this, new patch versions of AWS-provided public components might be automatically deployed to your core devices if you add new devices to a thing group, or you update the deployment that targets those devices. Some automatic updates, such as a nucleus update, can cause your devices to restart unexpectedly.

To prevent unintended updates for a component that is running on your device, we recommend that you directly include your preferred version of that component when you create a deployment. For more information about update behavior for AWS IoT Greengrass Core software, see Update the AWS IoT Greengrass Core software (OTA).

Component Details
Greengrass nucleus

Version 2.0.4 of the Greengrass nucleus is available.

New features
  • Enable HTTPS traffic over port 443. You can use the new greengrassDataPlanePort configuration parameter for version 2.0.4 of the nucleus component to configure HTTPS communication to travel over port 443 instead of the default port 8443. For more information, see Configure HTTPS over port 443.

  • Add the work path recipe variable. You can use this recipe variable to get the path to components' work folders, which you can use to share files between components and their dependencies. For more information, see the work path recipe variable.

Bug fixes and improvements
  • Prevent the creation of the token exchange AWS Identity and Access Management (IAM) role policy if a role policy already exists.

    As a result of this change, the installer now requires the iam:GetPolicy and sts:GetCallerIdentity when run with --provision true. For more information, see Minimal IAM policy for installer to provision resources.

  • Correctly handle the cancellation of a deployment that has not yet been registered successfully.

  • Update the configuration to remove older entries with newer timestamps when rolling back a deployment.

  • Additional minor fixes and improvements. For more information, see the changelog on GitHub.