Skip to content

AWS_ENDPOINT_URL env variable is not respected after the latest releaseΒ #7203

@lbeschastny

Description

@lbeschastny

Checkboxes for prior research

Describe the bug

AWS_ENDPOINT_URL is no longer picked up automatically from the env.

After some digging I pinpointed this to @smithy/[email protected].

Regression Issue

  • Select this option if this issue appears to be a regression.

SDK version number

@aws-sdk/[email protected], @aws-sdk/[email protected]

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

v22.13.1

Reproduction Steps

Set AWS_ENDPOINT_URL to any custom value and try using DynamoDBClient:

const client = new DynamoDBClient();

Observed Behavior

Requests are sent to the default endpoint

Expected Behavior

AWS_ENDPOINT_URL should be respected

Possible Solution

Either pass it to DynamoDBClient explicitly:

const client = new DynamoDBClient({ endpoint: process.env.AWS_ENDPOINT_URL }); // this still works

or use older @smithy/middleware-endpoint version:

  "overrides": {
    "@smithy/middleware-endpoint": "4.1.13"
  }

Additional Information/Context

I already opened an issue in smithy-typescript repo, but I decided to open one here as well since it affects the sdk.

Original issue: smithy-lang/smithy-typescript#1645

Metadata

Metadata

Assignees

Labels

bugThis issue is a bug.closing-soonThis issue will automatically close in 4 days unless further comments are made.p1This is a high priority issuepotential-regressionMarking this issue as a potential regression to be checked by team member

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions