2 Answers
- Newest
- Most votes
- Most comments
0
Hello.
I think the answer at the URL below is relevant.
I think it depends on how you use SQS, but I think the number of API executions will increase depending on the computing that polls the queue, etc.
https://repost.aws/questions/QUJoEXZRfNSQucfw18GSUkhQ/sqs-per-request-billing-way-above-actual-usage#ANudXB4pT6Tb-A4r17I5ayMg
0
Use it to receive Amazon Marketing Stream messages, receive messages through boto3's api receive_message, store and delete messages in batches after receiving them.
answered 2 years ago
Relevant content
- asked 2 years ago
- asked 4 years ago
- asked 3 years ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 2 years ago
There is no Lambda function used in the queue. Is this lambda function the default? Why can't it be displayed on the page? Now even if I don't call the API request, the cost is still increasing. Is this the reason? So many requests every month even if there is no news?
Could you please tell me the configuration around SQS in a little more detail? How do you process SQS messages? Requests are made in the process of sending messages to SQS, polling messages, and deleting messages. Therefore, charges may increase depending on the polling interval and message volume.
It is also possible that payload size is increasing the billed request count. Note from the SQS pricing page (https://aws.amazon.com/sqs/pricing/): "Size of Payloads - Each 64 KB chunk of a payload is billed as 1 request (for example, an API action with a 256 KB payload is billed as 4 requests)."