With AWS IoT Core, you pay only for what you use with no minimum fees or mandatory service usage. You are billed separately for usage of Connectivity, Messaging, Device Shadow usage (device state storage), Registry usage (device metadata storage), and Rules Engine usage (message transformation and routing). This approach provides you with transparency and a low price regardless of your workload type, because you only pay for the specific AWS IoT Core components you use.

Estimate your monthly bill using the AWS IoT Core Calculator.

Pricing at a Glance

Connectivity

Connectivity provides a secure, authenticated connection between your devices and AWS IoT Core. Connectivity is metered in 1 minute increments and is based on the total time your devices are connected to AWS IoT Core.

Connectivity Pricing (per million minutes of connection)

US East

(N.Virginia)

US East

(Ohio)

US West

(Oregon)

EU

(Ireland)

EU

(Frankfurt)

EU

(London)

APAC

(Mumbai)

APAC

(Sydney)

APAC

(Seoul)

APAC

(Tokyo)

APAC

(Singapore)

$0.080
$0.080 $0.080 $0.080 $0.096 $0.096 $0.092 $0.132 $0.096 $0.120 $0.132

For example, in the US East (N. Virginia) region you pay $0.042 per device per year (1 connection * $0.08/1,000,000 minutes of connection * 525,600 minutes/year) for 24/7 connectivity. In order to maintain connectivity, devices may send keep-alive (“Ping”) messages at frequencies ranging from 20 minutes to every 30s, and you do not incur any additional cost for these messages. Details

Messaging

Messages transport device data to and from AWS IoT Core. Messaging is metered by the number of messages transmitted between your devices and AWS IoT Core.

Messaging Pricing (per million messages)

Monthly Message Volume

US East  

(N.Virginia)

US East

 (Ohio)   

US West

(Oregon)

EU

(Ireland)

EU

(Frankfurt)

EU

(London)

APAC

(Mumbai)

APAC

(Sydney)  

APAC

(Seoul)   

APAC

 (Tokyo)   

APAC

(Singapore)

Up to 1 billion messages $1.00 $1.00 $1.00 $1.00 $1.20 $1.20 $1.05 $1.65 $1.20 $1.50 $1.65
Next 4 billion messages
$0.80 $0.80 $0.80 $0.80 $0.96 $0.96 $0.84 $1.32 $0.96 $1.20 $1.32
Over 5 billion messages $0.70 $0.70 $0.70 $0.70 $0.84 $0.84 $0.74 $1.16 $0.84 $1.05 $1.16

You may send and receive messages up to 128 kilobyte (KB) in size. Messages are metered in 5 KB increments. For example, an 8 KB message is metered as two messages. Details

Device Shadow & Registry

The Device Shadow stores the desired state or actual state of a device, and the Registry is used to name and manage devices. Use of Device Shadow and Registry is metered by the number of operations that access or modify Device Shadow or Registry data.

Device Shadow and Registry Pricing (per million operations)

US East

(N.Virginia)

US East

(Ohio)

US West

(Oregon)

EU

(Ireland)

EU

(Frankfurt)

EU

(London)

APAC

(Mumbai)

APAC

(Sydney)

APAC

(Seoul)

APAC

(Tokyo)

APAC

(Singapore)

$1.25
$1.25 $1.25 $1.25 $1.50 $1.50 $1.31 $1.75 $1.50 $1.75 $1.88

Device Shadow and Registry operations are metered in 1 KB increments of the Device Shadow or Registry record size. For example, an update to a 1.5 KB Device Shadow record is metered as two operations. Details

Rules Engine

Rules Engine allows you to transform device data using arithmetic operations or external functions such as AWS Lambda, and then route the data to an AWS service such as Amazon S3, Amazon DynamoDB, or Amazon Kinesis. Rules Engine use is metered for each time a rule is triggered, and for the number of actions executed within a rule, with a minimum of one action per rule.

Rules Engine Pricing (per million rules triggered / per million actions executed)

 

US East

(N.Virginia)

US East

 (Ohio)   

US West

(Oregon)

EU

(Ireland)

EU

(Frankfurt)

EU

(London)

APAC

(Mumbai)

APAC

(Sydney)

APAC

(Seoul)

APAC

(Tokyo)

APAC

Singapore)

Rules triggered $0.15
$0.15 $0.15 $0.15 $0.18 $0.18 $0.158 $0.248 $0.18 $0.225 $0.248
Actions executed $0.15 $0.15 $0.15 $0.15 $0.18 $0.18 $0.158 $0.248 $0.18 $0.225 $0.248

Rules that process a message in excess of 5 KB are metered at the next multiple of the 5 KB size. For example, a rule that processes an 8 KB message is metered as two rules. Details

AWS Free Tier with AWS IoT Core
  • 2,250,000 minutes of connection
  • 500,000 messages
  • 225,000 Registry or Device Shadow operations
  • 250,000 rules triggered and 250,000 actions executed

For example, the Free Tier would allow you to run a 50-device workload, where each device:

  • Connects for 24 hours a day
  • Exchanges 300 messages per day (message size 5 KB or smaller)
  • Makes 130 Registry or Device Shadow operations per day (Registry or Device Shadow record size 1 KB or smaller)
  • Triggers 150 rule executions per day that invoke one action (processed message size 5 KB or smaller)

The AWS Free Tier is available to you for 12 months starting with the date on which you create your AWS account. When your free usage expires or if your application use exceeds the free usage tiers, you simply pay the above rates. The free usage tier applies across all AWS Regions except GovCloud (US). Your usage is calculated each month across all regions and is automatically applied to your bill. Note that free usage does not accumulate from one billing period to the next.

Pricing Examples for AWS IoT Core Components

Connectivity Charges

Pricing Example 1

Your cost to connect 10,000 devices to AWS IoT Core for 30 days would be calculated as follows:

  • Minutes of connection = 10,000 connections * 60 minutes/hour * 24 hours/day * 30 days = 432,000,000 minutes of connection
  • Total Charges = 432,000,000 minutes of connection * $0.08/1,000,000 minutes of connection = $34.56

Pricing Example 2

Your cost to connect 10,000 devices to AWS IoT Core for 15 minutes each hour for 30 days would be calculated as follows:

  • Minutes of connection = 10,000 connections * 15 minutes/hour * 24 hours/day * 30 days = 108,000,000 minutes of connection
  • Total Charges = 108,000,000 minutes of connection * $0.08/1,000,000 minutes of connection = $8.64
Messaging Charges

Pricing Example 1

Over 30 days, your device publishes one 2 KB message every hour to AWS IoT Core, and AWS IoT Core then delivers each message to 5 other devices. Your charges would be calculated as follows:

Publishing cost to the AWS IoT Core

  • Published message count: 1 message/hour * 24 hours/day * 30 days = 720 messages
  • Published message charges: 720 messages * $1/1,000,000 messages = $0.00072

Delivery cost to Devices

  • Delivered message count: 5 messages/hour * 24 hours/day * 30 days = 3,600 messages
  • Delivered message charges: 3,600 messages * $1/1,000,000 messages = $0.0036

Total Charges

  • Total Charges = Published message charges + Delivered message charges
  • Total Charges = $0.00072 + $0.0036 = $0.00432

Pricing Example 2

Over 30 days, your device publishes ten 8 KB messages every hour to AWS IoT Core. Your charges would be calculated as follows:

Publishing cost to the AWS IoT Core

  • Since each message is larger the 5 KB, it is metered as 2 (5 KB) messages.
  • Published message count: 2 * (10 messages/hour * 24 hours/day * 30 days) = 14,400 messages
  • Total Charges = 14,400 messages * $1/1,000,000 messages = $0.01444
Device Shadow & Registry Charges

Pricing Example 1

Your devices trigger 1 million Device Shadow updates. The Device Shadow record size for each update is 1.5 KB. Your charges would be calculated as follows:

  • Since the Device Shadow size exceeds 1 KB, operations are metered at the next KB multiple (2 KB) as two operations.
  • Device Shadow Charges = 2 operations * 1,000,000 * $1.25/1,000,000 operations = $2.50

Pricing Example 2

Over 30 days, you call the ListThing API 100 times. Each time, the API returns 500 records and the size of each record is 1 KB. Your charges would be calculated as follows:

  • Registry requests = 100 requests * 500 = 50,000 requests
  • Registry Charges = 50,000 requests * $1.25/1,000,000 requests = $0.0625
Rules Engine Charges

Pricing Example 1

Your devices trigger 1 million rules. Each rule forwards data to Amazon S3, thereby invoking one action. Your charges would be calculated as follows:

  • Rules charges = 1,000,000 rules triggered * $0.15/1,000,000 rules triggered = $0.15
  • Actions charges = 1,000,000 rules triggered * 1 action executed/rule triggered * $0.15/1,000,000 actions executed = $0.15
  • Total Rules Engine Charges = Rules charges + Actions charges = $0.15 + $0.15 = $0.30

Pricing Example 2

Your devices trigger 1 million rules. Each rule calls an external function and then forwards data to Amazon S3, thereby invoking two actions. Your charges would be calculated as follows:

  • Rules Charges = 1,000,000 rules triggered * $0.15/1,000,000 rules triggered = $0.15
  • Actions Charges = 1,000,000 rules triggered * 2 actions executed/rule triggered * $0.15/1,000,000 actions executed = $0.30
  • Total Rules Engine Charges = Rules Charges + Actions Charges = $0.15 + $0.30 = $0.45

Pricing Example for a Workload Using All AWS IoT Core Components

100,000 devices maintain a constant connection to AWS IoT Core for 30 days. Each day, each device exchanges 325 messages of 1 KB in size. Of the 325 messages exchanged, 100 trigger a Device Shadow update and 200 trigger a rule that executes one action. Your charges would be calculated as follows:

CONNECTIVITY CHARGES

  • Minutes of connection = 100,000 connections * 60 minutes/hour * 24 hours/day * 30 days = 4,320,000,000 minutes of connection
  • Connectivity charges = 4,320,000,000 minutes of connection * $0.08/1,000,000 minutes of connection = $345.60

MESSAGING CHARGES

  • Messages = 100,000 devices * 325 messages/device-day * 30 days = 975,000,000 messages
  • Messaging charges = 975,000,000 messages * $1.00/1,000,000 messages = $975.00

DEVICE SHADOW & REGISTRY CHARGES

  • Device Shadow Requests = 100,000 devices * 100 requests/device-day * 30 days = 300,000,000 requests
  • Device Shadow Size is less than 1 KB, so it is rounded up to the nearest KB (1 KB)
  • Device Shadow Charges = 300,000,000 requests * $1.25/1,000,000 operations = $375.00

RULES ENGINE CHARGES  

  • Rules Triggered = 100,000 devices * 200 rules triggered/device-day * 30 days = 600,000,000 rules triggered
  • Actions Executed = 600,000,000 rules triggered * 1 action executed/rule triggered = 600,000,000 actions executed
  • Rules Charges = 600,000,000 rules triggered * $0.15/1,000,000 rules triggered = $90.00
  • Actions Charges = 600,000,000 actions executed * $0.15/1,000,000 actions executed = $90.00
  • Total Rules Engine charges = $90.00 + $90.00 = $180.00

TOTAL WORKLOAD CHARGES

  • Total Charges = $346.60 + $975.00 + $375.00 + $180.00 = $1,876.60

 

Discover more AWS IoT Core resources

Visit the resources page
Ready to get started?
Sign up
Have more questions?
Contact us