1 Answer
- Newest
- Most votes
- Most comments
0
Hi,
For IoTDataPlaneClient
within Lambda, if Lambda's are being reused, moving the instantiation of client outside of the main event handler can reduce subsequent calls. Then if the same Lambda is called again, that client can be reused.
What I haven't investigated is how the underlying client managed state, and if those parameters can be adjusted. The data plane client is making HTTP POSTs for the different operations such as Publish, so creating an HTTP persistent connection could be an approach to keep a connection pool open. Not a C++ expert, but I found this example that may help.
answered a year ago
Relevant content
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
Thanks for the reply,
Would there be a way to maintain the connection across Lambda invocations?
Apologies, I misread this as a full MQTT connection (when I definitely saw the reference to
IoTDataPlaneClient
too! :) ). I've updated my answer with guidance on that.