Connectivity

Your device can ping as often as every 30s, with no charge for MQTT PINGREQ or PINGRESP messages. Pinging more frequently may result in the AWS IoT device gateway not responding to PINGREQ.

Messaging

MQTT Message Metering

MQTT CONNECT Metered as the size of the message including "Will" topic size and "Will" message payload

MQTT PUBACK

(received from device)

Metered as a single 5 KB message
MQTT SUBSCRIBE Metered on the size of the topic submitted in the Subscribe message

MQTT PUBLISH

(received from device)

Metered on the size of the payload and topic in bytes

MQTT PUBLISH

(sent by service)

Metered on the size of the payload and topic in bytes

The following MQTT messages are excluded from metering:

  • MQTT PINGREQ
  • MQTT PINGRESP
  • MQTT DISCONNECT
  • MQTT CONNACK
  • MQTT PUBACK (sent by service)
  • MQTT SUBACK
  • MQTT UNSUBSCRIBE

MQTT messages transferred inside a WebSocket connection are metered like MQTT messages inside a mutually authenticated TLS connection.

HTTP Request and Response Metering

Requests Metered on the number of 5 KB messages needed to encode the body section of the HTTP request
Responses Metered on the number of 5 KB messages needed to encode the body section of the HTTP response
Negative Responses
If HTTP responses with HTTP response codes in the 4xx and 5xx range contains a body, AWS IoT meters the number of 5 KB message needed to encode the response body
Device Registry

You are charged for a Device Registry operation each time you make a call to one of the following APIs:

  • AddThingToThingGroup
  • AttachThingPrincipal
  • CreateThing
  • CreateThingGroup
  • CreateThingType
  • DescribeThing
  • DescribeThingGroup
  • DescribeThingType
  • ListChildThingGroups
  • ListPrincipalThings
  • ListThingGroups
  • ListThingGroupsForThing
  • ListThingPrincipals
  • ListThings
  • ListThingsInThingGroup
  • ListThingTypes
  • UpdateThing
  • UpdateThingGroup
  • UpdateThingGroupsForThing

Note that for all List operations, metering takes into account total size of all records returned by API call. For example, if a ListThings API call returns (50) 2 KB Things from Device Registry, your request Is charged for (100) 1K increments, and is metered as 100 requests. If you opt-in for Registry Events, any update messages will be subject to Messaging charges.

Device Shadow

Device Shadow operations are metered when you make an API call to GetThingShadow or UpdateThingShadow, or when an MQTT message creates, updates, or gets a Device Shadow. If you opt-in for Shadow updates, the update messages will be subject to Messaging charges.

Rules Engine

A rule can invoke up to 10 actions, where an action is an external function call (i.e. Get_Thing_Type()), or a call to an external service (Amazon S3, Amazon Kinesis, Amazon SNS, etc.). Arithmetic and logical SQL functions are not metered as actions. Rules that process a message generated by AWS IoT are metered as a single rule, regardless of message size. For example, a 7KB shadow document may publish a /delta or /documents message that is quite large, however any rules triggered by such an update will be metered as if the message were 5KB.

Discover more AWS IoT Core resources

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