In the aws-sdk v3 docs for SQSClient.destroy it states

Destroy underlying resources, like sockets. It's usually not necessary to do this. However in Node.js, it's best to explicitly shut down the client's agent when it is no longer needed. Otherwise, sockets might stay open for quite a long time before the server terminates them.

In a Node.js lambda environment, would you say it's necessary to call destroy after processing each time? Seems like unnecessary tear-down and then client creation on next invocation if warm

Yeah you already have the lambda runtime cleaning up idle things

Ok, cool, thanks