Yenfry Herrera Feliz

Hi @jaw111, thanks for replying back. Would it be possible for you to check if with the latest version the issue persist? Thanks!

Hi @llh-check, is this still an issue for you?, if so, would it be possible for you to upgrade to a most recent TS version?. Basically this issue happens because...

Hi people, the intention of this warning is to let you all know about our plans regarding the AWS SDK for JavaScript V2, however, I agree with all of you...

Hi @gokul-ilango, sorry to hear about your issues. I think this behavior may be caused by the default credentials resolution, which will go over each credentials provider set in the...

A possible workaround would be: ```js import https from "https"; const keepAliveMsecs = 5 * 1000; const tempHttpsRequestFn = https.request; https.request = (options, callback) => { const clientRequest = tempHttpsRequestFn(options,...

Hi @letto4135, thanks for opening this issue. Basically this is not an issue with the SDK, rather is just that you are not implementing any logic to stop the request...

Hi @mahmoud-triki, thanks for opening this issue. I agree with this suggestion. I will mark this issue as feature-request and to be reviewed so it can be further addressed. Thanks!

Related: https://github.com/aws/aws-sdk-js/issues/4150

Hi @shaangidwani, thanks for opening this issue. I tried to reproduce this but as you said seems it may happen sporadically. I will investigate this further to see if I...

Hi @ochoav, sorry to hear about your issues. I can confirm the reported behavior. For now the workaround that you have used is correct, basically the parameter signingRegion from getSignedUrl...