AWS IoT Core cost: messages, connection minutes, and rules
IoT Core bills connectivity per million connection-minutes, messaging per million messages, and rules-engine actions, plus device shadow and registry operations. Chatty devices and heavy rule fan-out drive the bill. Here is the model.
Quick answer
IoT Core bills connectivity per million connection-minutes, messaging per million messages (sized in 5 KB blocks), rules-engine actions triggered, and device shadow and registry operations. Chatty devices sending frequent or large messages, and rules that fan out to many actions, drive the bill, so batch telemetry, size messages efficiently, and scope rules tightly.
AWS IoT Core connects devices to the cloud, and its pricing has several components that each scale with device behavior. For a fleet of many devices sending frequent telemetry, the message and rule volume is what determines cost, so the levers are about how much your devices talk and what happens when they do.
The components
| Component | Bills for |
|---|---|
| Connectivity | Per million connection-minutes |
| Messaging | Per million messages (5 KB blocks) |
| Rules engine | Per rule triggered and action executed |
| Device shadow / registry | Per operation |
Connectivity is billed for the minutes devices stay connected. Messaging is per message, with messages counted in 5 KB increments, so a large message counts as several. The rules engine bills per rule triggered and each action it takes. Device shadow and registry operations add per-call charges.
What drives the bill
Chatty devices are the main cost driver: a fleet sending telemetry every second produces enormous message volume, and large payloads count as multiple messages. Rules that fan out each message to several actions (a database write, a Lambda, a notification) multiply downstream cost, and those downstream services often cost more than IoT Core itself.
Controlling IoT Core cost
Batch telemetry so devices send fewer, fuller messages rather than many tiny ones, keep payloads under the 5 KB block where possible, scope rules so only relevant messages trigger actions, and optimize the downstream services rules invoke. As with Cloud Tasks, the messaging layer is often cheaper than the compute it drives, so watch the rule actions.
FAQ
How is AWS IoT Core priced?
By connectivity (per million connection-minutes), messaging (per million messages counted in 5 KB blocks), rules-engine actions (per rule triggered and action executed), and device shadow and registry operations. Cost scales with how much your device fleet connects and communicates.
What drives IoT Core cost?
Chatty devices: a fleet sending frequent telemetry produces large message volume, and large payloads count as multiple 5 KB messages. Rules that fan out each message to several actions multiply cost, and the downstream services those actions invoke often cost more than IoT Core itself.
How do I reduce IoT Core cost?
Batch telemetry so devices send fewer, fuller messages, keep payloads under the 5 KB block where possible, scope rules so only relevant messages trigger actions, and optimize the downstream services (Lambda, databases) that rules invoke. Fewer, leaner messages and tighter rules are the main levers.
How are IoT Core messages counted?
In 5 KB blocks. A message up to 5 KB counts as one; a larger message counts as multiple. So sending large payloads inflates the message count and cost. Keeping messages compact, under 5 KB, keeps each as a single billed message.
Does the IoT rules engine cost extra?
Yes, per rule triggered and per action executed. A rule that fans a single message out to several actions (database write, Lambda invocation, notification) bills for each, and the invoked services add their own cost. Scope rules so only relevant messages trigger the actions you need.
Does C3X estimate IoT Core cost?
IoT Core cost is driven by connection-minutes, message volume, and rule actions, which are usage inputs tied to device behavior. C3X prices the surrounding infrastructure, including the downstream services rules invoke, and you model device telemetry to estimate the IoT charges.
What to do next
Estimate the infrastructure behind your IoT fleet before you build it. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.
Pricing references
Related posts
- AWS AppSync cost: per query, per real-time message, per connection
AppSync bills GraphQL query and data-modification operations per million, real-time subscription messages per million, and connection-minutes. Chatty clients and broad subscriptions drive the bill. Here is how the managed-GraphQL pricing works.
- AWS Amplify Hosting cost: build minutes, hosting, and SSR compute
Amplify Hosting bills build minutes, stored artifacts, data served, and server-side rendering compute. For a static site it is cheap; SSR and heavy traffic are where cost grows. Here is the breakdown and where to cut.
- AWS Site-to-Site VPN cost: cheap per connection, plus egress
Site-to-Site VPN bills about $0.05 per connection-hour (roughly $36/month) plus standard data transfer out. It is a cheap, quick way to connect on-premises to AWS over the internet. Here is the model and when to prefer Direct Connect.
- AWS Verified Access cost: per app connection per hour plus data
Verified Access bills per application connected per hour plus data processed, giving zero-trust access to internal apps without a VPN. Many connected apps and high traffic drive the bill. Here is the model.
Share this post
Try C3X on your own Terraform
Free and open source. No API key required. One command to install, one command to estimate.