Question: Default keep alive internal is shorter than the service limit

[yuma-m]

Confirm by changing [ ] to [x] below:

• I've searched for previous similar issues and didn't find any solution

Platform/OS/Device
No specific platform.

Describe the question
The default keep alive time is 6 seconds in Device SDK Python v2.

aws-iot-device-sdk-python-v2/samples/pubsub.py

Line 124 in f107ecf

keep_alive_secs=6,

However, according to the IoT Core limit, keep alive interval should be between 30 ~ 1200 seconds.

Your device can ping as often as every 30s, with no charge for MQTT PINGREQ or PINGRESP messages.

In addition, it looks PING interval shorter than 30s can be charged according to the pricing page.

What is the intention for the default keep alive interval (6 seconds) in Device SDK? Should it be modified to 30 seconds or longer?

[bretambrose]

The default keep alive is here: https://github.com/aws/aws-iot-device-sdk-python-v2/blob/main/awsiot/mqtt_connection_builder.py#L203

That being said, it's reasonable to update the samples to not have a keep alive below the IoT minimum. If you wanted to make a PR, we'd happily take it.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.