Billing groups - AWS IoT Core

Billing groups

AWS IoT doesn't allow you to directly apply tags to individual things, but it does allow you to place things in billing groups and to apply tags to these. For AWS IoT, allocation of cost and usage data based on tags is limited to billing groups.

AWS IoT Core for LoRaWAN resources, such as wireless devices and gateways, can't be added to billing groups. However, they can be associated with AWS IoT things, which can be added to billing groups.

The following commands are available:

The AWS IoT Wireless API provides these actions to associate wireless devices and gateways with AWS IoT things.

Viewing cost allocation and usage data

You can use billing group tags to categorize and track your costs. When you apply tags to billing groups (and so to the things they include), AWS generates a cost allocation report as a comma-separated value (CSV) file with your usage and costs aggregated by your tags. You can apply tags that represent business categories (such as cost centers, application names, or owners) to organize your costs across multiple services. For more information about using tags for cost allocation, see Use Cost Allocation Tags in the AWS Billing and Cost Management User Guide.


To accurately associate usage and cost data with those things you have placed in billing groups, each device or application must:

  • Be registered as a thing in AWS IoT. For more information, see Managing devices with AWS IoT.

  • Connect to the AWS IoT message broker through MQTT using only the thing's name as the client ID. For more information, see Device communication protocols.

  • Authenticate using a client certificate associated with the thing.

The following pricing dimensions are available for billing groups (based on the activity of things associated with the billing group):

  • Connectivity (based on the thing name used as the client ID to connect).

  • Messaging (based on messages inbound from, and outbound to, a thing; MQTT only).

  • Shadow operations (based on the thing whose message triggered a shadow update).

  • Rules triggered (based on the thing whose inbound message triggered the rule; does not apply to those rules triggered by MQTT lifecycle events).

  • Thing index updates (based on the thing that was added to the index).

  • Remote actions (based on the thing updated).

  • AWS IoT Device Defender detect reports (based on the thing whose activity is reported).

Cost and usage data based on tags (and reported for a billing group) doesn't reflect the following activities: