AWS Greengrass Pricing

With AWS Greengrass, you pay only for what you use. You are charged based on the number of Greengrass Core devices that interact with the AWS Cloud in a given month. The Greengrass free tier includes 3 free Greengrass Cores for a year. There is no charge for AWS IoT SDK enabled devices connected to the Greengrass Core device.

3 Devices

Free for 1 Year with the AWS Free Tier

3 - 10,000 Devices

AWS Greengrass has two pricing options: Pay as you go or receive a 22% savings for annual commitments.

AWS Greengrass includes two pieces of client software: Greengrass Core, the runtime that provides local AWS Lambda, messaging, device shadows, and security, and the AWS IoT Device SDK, which lets devices interact with Greengrass Core via the local network.

An AWS Greengrass Core is active for the month when it authenticates with AWS. You can locally connect Devices to your Greengrass Cores for no additional charge. A Greengrass Core is considered inactive when it does not connect with AWS for 30 days, even if the device continues to operate locally.

Additional Charges

You may incur additional charges with AWS Greengrass if your applications utilize other AWS services or transfers data. For example, if AWS Greengrass transmits data to or from Amazon S3, you will be billed for the read/write requests and the data stored in Amazon S3.

For details on AWS service pricing, see the pricing section of the relevant AWS service detail pages. Links to pricing for some of the commonly used services are listed below.

Except as otherwise noted, our prices are exclusive of applicable taxes and duties, including VAT and applicable sales tax. For customers with a Japanese billing address, use of AWS is subject to Japanese Consumption Tax.

Pricing Examples

Example 1 - The following example assumes there are 3 AWS Greengrass Core devices that are active for 11 months:

Device A - An AWS Greengrass Core device is powered on in January and powered down at the end of November. When the device is powered on, it downloads new Lambda functions when they are available and continuously synchronizes its state via device shadows.

Device B - An AWS Greengrass Core device sits inactive on a warehouse shelf in January, but is sold and powered on in February. When the device is powered on, it uses local Lambdas to summarize 1-second metrics into 5-minute metrics and uploads the 5-minute metrics to AWS IoT or Kinesis.

Device C - An AWS Greengrass Core is powered on in January and stays powered on all year. It has no internet connectivity for the month of December, and so never interacts with the cloud in December.

Example 2 – An AWS Greengrass Core (Device A) is destroyed at the end of January, and Greengrass Core (Device B) is powered on in February to replace it. This counts as 1 active device in January, and 1 active device in February.

Example 3 – One AWS Greengrass Core (Device A) interacts with 10 Greengrass-aware devices via the local network to respond quickly to events and send appropriate updates to the cloud. This counts as 1 active device. The device is active for 12 months. The customer in the example has opted for an annual commitment ($0.12417/month) to receive a savings of 17.5% over the pay as you go model.