John L.

Hi @camhart - thanks for reaching out and your feedback on the documentation. I'm glad you were able to resolve the issue and I couldn't find the internal ticket reference...

Closing as the original issue had been resolved. Please refer to this [docs](https://github.com/aws/aws-sdk-js-v3/blob/main/supplemental-docs/CLIENTS.md#nodejs-requesthandler) "A note on socket exhaustion".

Hi @lromor - thanks for reaching out. As you're probably aware, this `RequestTimeTooSkewed` error is due to the mismatch between the server time and current time. In order for us...

Hi there - apologies for the extended delay in providing a response. It appears that this issue needs to be addressed by the service team, as these models are generated...

Hey all - checking in from SDK team. Reviewing previous comments, I noted that the problem couldn't be replicated and someone suggested that turning off IPv6 fixed the issue. It...

Hi @satyaprakashpatel - can you share your code that would give us more insight into the reported behavior? Can you also elaborate on your title as which part of documentation...

Apologies for the prolonged delay in responding. Upon further investigation, it appears that the observed behavior is related to the CloudFront service rather than the AWS SDK. Since the service...

Hi @just-boris - thanks for submitting this feature request. I understand that this was raised internally and will be further discussed within JavaScript SDK team for potential implementation. A few...

Hi @agnoam - apologies for the long wait. The behavior you're seeing is likely due to the way the AWS SDK is handling the `s3ForcePathStyle` and `s3BucketEndpoint` options when used...

@gauthampkrishnan - Can you share the code you are working on so that we can better assist you? Here's docs on SDK retry strategies and behavior for your reference: https://github.com/aws/aws-sdk-js-v3/blob/main/supplemental-docs/CLIENTS.md#retry-strategy-retrystrategy-retrymode-maxattempts