- Newest
- Most votes
- Most comments
Thanks for the reply. Re the payload size. The significant cost is in cellular data. So the 4k-6k overhead is increasing my data cost by a factor of at least 6. AWS core messaging costs are certainly a consideration but at the moment far outweighed by the data costs. To the point that using AWS IOTCore as my endpoint for my fleet of IOT devices is not really viable.
I'd be interested if there are alternative thought regarding this.
I don't currently have an account manager I don't think. Is there another way to get this escalated?
Thanks, Karl
Hello, did you manage to find a work-around for this? We are also facing similar issues with data usage...
Hi. TLS session resumption is not presently supported by AWS IoT Core. The benefit of the feature is clear. If you have an Account Manager, please request this feature with them.
You mention that a typical message is only 100 bytes. Please be aware that MQTT messages are metered in 5KB increments. I realize this may not be practical for your application, but if you could batch your messages (and hence connect less frequently), you would reduce both your cellular network data usage and your AWS IoT costs.
Relevant content
- asked 11 days ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 9 months ago
I had a similar issue, and I ended up staying connected instead of connecting again every time. You probably could adjust the cellular network parameters (NB-IoT?) to stay in low-power mode while connected. This also has the advantage of having an always-on downlink in case you need it.