AWS SDK v3 no retry on connection issue

[wanching0730]

Checkboxes for prior research

• I've gone through Developer Guide and API reference
• I've checked AWS Forums and StackOverflow.
• I've searched for previous similar issues and didn't find any solution.

Describe the bug

The connectTimeout attribute in v2 no longer supported in v3, there is no way to set connection timeout value. The default connection timeout is 120s which is too long and it's more than the Lambda timeout that we set. Kindly assist.

SDK version number

@aws-sdk/client-lambda@3.289.0, @aws-sdk/client-dynamodb@3.128.0, @aws-sdk/client-s3@3.289.0, @aws-sdk/client-secrets-manager@3.289.0

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

node v18.15.0

Reproduction Steps

const requestHandler = new NodeHttpHandler({
  requestTimeout: 1500,
});
const secretManager = new SecretsManagerClient({
  endpoint: SECRETS_MANAGER_VPCE,
  requestHandler,
  maxAttempts: 3,
  region: 'ap-southeast-1'
});

return await secretManager.send(new GetSecretValueCommand({ SecretId: secretName }));

Observed Behavior

Expected Behavior

There should be a way to set connection timeout in v3, which is the replace the connectTimeout in HttpOptions in v2.

Possible Solution

No response

Additional Information/Context

No response

[RanVaknin]

Hi @wanching0730 ,
We are working on un-deprecating connectionTimeout. Can you please an older version of the SDK in the meantime while we work to re-introduce this config option?

Thank you very much,
Ran~

[trivikr]

The fix to undeprecate connectionTimeout and reintroduce functionality was pushed in PR #4669
It'll be released with v3.322.0 around 1pm Pacific either on Thu 04/27 or Fri 04/28

In the meantime, please use <= v3.295.0 as a workaround.

[wanching0730]

Noted on that, thank you very much

[trivikr]

The fix was released in https://github.com/aws/aws-sdk-js-v3/releases/tag/v3.321.1

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.