Understanding some API Operations in IoT Core Billing

0

Hello,

We have a setup with devices broadcasting device shadows over MQTT to IoT core, and some message routing rules set up. I am looking at the IoT bill broken down by "API Operation". These API Operations appear when filtering by Service = IoT.

  1. HTTP.Response - I'm struggling to understand what this bill represents. Is this responses from http endpoints hit by message routing rules?
  2. MQTT.Receive - is this a charge for clients receiving mqtt messages? Are we also charged for messages received by the message routing rules?

Thanks for your help

feita há 2 meses220 visualizações
2 Respostas
1
Resposta aceita

Hi,

You can find additional details on meter and cost for IoT Core operations here. Some additional content to your two points:

  1. HTTP.Response - I'm struggling to understand what this bill represents. Is this responses from http endpoints hit by message routing rules?

Yes, this would be metered responses for negative (400 and 500) responses:

If HTTP responses with HTTP response codes in the 4xx and 5xx range contains a body, AWS IoT Core meters the number of 5 KB message needed to encode the response body

And for your second API Operation question:

  1. MQTT.Receive - is this a charge for clients receiving mqtt messages? Are we also charged for messages received by the message routing rules?

Messages sent and received by an MQTT client are metered (see the section in the above link under MQTT Message Metering). The primary ones will be MQTT PUBLISH, which can be from a device publishing to IoT Core, or from IoT Core (service) publishing out to a device.

As Rick also mentioned, you can open a support case for additional insights into your specific account costs. It's also good to review the Cost Optimization pillar for IoT that goes into details on how to architecture and observe costs. Please let us know if this answers your question!

AWS
Gavin_A
respondido há 2 meses
profile picture
ESPECIALISTA
avaliado há 2 meses
  • Hi Gavin, thank you for your insight. This does help clarify things. Particularly understanding the http response billing for negative responses from routing rules. That clarifies the bill there. I was struggling to understand the MQTT.Receive bill because it seemed too high for our volume, until I realized that our devices are also subscribed to the /shadow/update/accepted topic, so that explains that portion. Thanks for your help!

0

Hello there,

I'm sorry to hear you're having issues with your bill. Our billing experts would be more then happy to assist with your AWS statement. Please contact our Support team by creating a case from our Support Center: http://go.aws/support-center.

- Rick N.

profile pictureAWS
ESPECIALISTA
respondido há 2 meses

Você não está conectado. Fazer login para postar uma resposta.

Uma boa resposta responde claramente à pergunta, dá feedback construtivo e incentiva o crescimento profissional de quem perguntou.

Diretrizes para responder a perguntas