Amazon IoT Core Pricing

Estimate your monthly bill for either region using the Amazon IoT Core Calculator.

See additional pricing details »

See additional pricing details »

Example 1

You have 10,000 devices that maintain constant connection to Amazon IoT Core in the China (Beijing) region for 30 days. The connectivity rate for the region is ¥0.72/1,000,000 minutes of connection. Your charges 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 Connectivity charges = 432,000,000 minutes of connection * ¥0.72 /1,000,000 minutes of connection = ¥311.04
  

Example 2

In this example the same 10,000 devices connect to Amazon IoT Core in the China (Beijing) region for just 15 minutes each hour, every hour for 30 days. Your charges 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 Connectivity charges = 108,000,000 minutes of connection * ¥0.72/1,000,000 minutes of connection = ¥77.76
  

Example 1

Imagine you have one device that publishes one 2 KB message every hour to Amazon IoT Core in the China (Beijing) region for 30 days. Amazon IoT Core then delivers each (2 KB) message to five other devices in the same region. The MQTT and HTTP messaging rate for the first one billion messages is ¥8.97/1,000,000 messages. Your charges would be calculated as follows:

Publishing cost to the Amazon IoT Core

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

Delivery cost to Devices

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

Total Messaging Charges

• Total messaging charges = Published message charges + Delivered message charges
  
• Total messaging charges = ¥0.0064584 + ¥0.032292 = ¥0.0387504

Example 2

For this example, you have one device that publishes ten 8 KB messages every hour to Amazon IoT Core in the China (Beijing) region for 30 days. Of those ten messages sent every hour, four are sent to Amazon IoT Core Rules Engine via Basic Ingest. Because in this example you are using MQTT or HTTP, you do not incur messaging charges for the four messages sent or received using the Basic Ingest reserved topic. The other six messages are published at the rate of ¥8.97/1,000,000 messages for the first one billion messages. Your messaging charges would be calculated as follows:

Publishing cost to the Amazon IoT Core

Since each message is larger than 5 KB, it is metered as two (5 KB) messages.

• Published message count via Basic Ingest: 2 metered messages * (4 messages/hour * 24hours/day * 30 days) = 5,760 messages
• Remaining published message count: 2 metered messages * (6 messages/hour * 24 hours/day * 30 days) = 8,640 messages
• Messaging charges for published messages via Basic Ingest: 5,760 messages * ¥0 = Free
• Messaging charges for remaining published messages: 8,640 messages * ¥8.97/1,000,000 messages = ¥0.0775008

Total messaging charges = Messaging charges for published messages via Basic Ingest + Messaging charges for remaining published messages = ¥0 + ¥0.0775008 = ¥0.0775008

Example 1

You have 100 devices that trigger a total of 1,000,000 Device Shadow updates in the China (Beijing) region. The Device Shadow record size for each update is 1.5 KB. The Device Shadow and Registry rate for the China (Beijing) region is ¥11.21/1,000,000 operations. 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.

Total Device Shadow charges = 2 operations * 1,000,000 updates * ¥11.21/1,000,000 operations = ¥22.42

Example 2

Your solution from above calls the ListThing API 100 times over 30 days. Each time, the API returns 500 records. The size of each record is 1 KB. Your charges would be calculated as follows:

Registry requests = 100 requests * 500 = 50,000 requests

Total Registry charges = 50,000 requests * ¥11.21/1,000,000 requests = ¥5.605

Example 1

You have 100 devices that trigger a total of 1,000,000 rules in the China (Beijing) region. Each rule forwards data to Amazon S3, thereby invoking one action. The rate for both the rules triggered and the actions executed in China (Beijing) is ¥1.35 (per million rules triggered / per million actions executed). Your charges would be calculated as follows:

• Rules triggered charges = 1,000,000 rules triggered * ¥1.35/1,000,000 rules triggered = ¥1.35
  
• Actions executed charges = 1,000,000 rules triggered * 1 action executed/rule triggered * ¥1.35/1,000,000 actions executed = ¥1.35
  

Total Rules Engine charges = Rules charges + Actions charges = ¥1.35 + ¥1.35 = ¥2.70

Example 2

For this example, the same 100 devices from above trigger a total of 1,000,000 rules in the China (Beijing) region. However, each also rule calls an external function and then forwards data to Amazon S3, thereby invoking two actions. Your charges would be calculated as follows:

• Rules triggered charges = 1,000,000 rules triggered * ¥1.35/1,000,000 rules triggered = ¥1.35
  
• Actions executed charges = 1,000,000 rules triggered * 2 actions executed/rule triggered * ¥1.35/1,000,000 actions executed = ¥2.70
  

Total Rules Engine Charges = Rules Charges + Actions Charges = ¥1.35 + ¥2.70 = ¥4.05

You have 100,000 devices that maintain a constant connection to Amazon IoT Core for 30 days in the China (Beijing) region. Each day, each device sends 325 messages of 1 KB in size. Of the 325 messages sent per device each day, 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.72/1,000,000 minutes of connection = ¥3,110.4

Messaging Charges

• Messages = 100,000 devices * 325 messages/device-day * 30 days = 975,000,000 messages
• Messaging charges = 975,000,000 messages * ¥8.97/1,000,000 messages = ¥8,745.75

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 * ¥11.21/1,000,000 operations = ¥3,363.0

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 triggered charges = 600,000,000 rules triggered * ¥1.35/1,000,000 rules triggered = ¥810.0
• Actions executed charges = 600,000,000 actions executed * ¥1.35/1,000,000 actions executed = ¥810.0
  

Total Rules Engine charges = ¥810.0 + ¥810.0 = ¥1620.0

Total Workload Charges

• Total charges = ¥3,110.4 + ¥8,745.75 + ¥3,363.0 + ¥1620.0 = ¥16,839.15

Please note, Amazon IoT Core does not involve the resale of telecommunication services and connectivity will be provided by third parties.