Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DynamoDB client url changed after 3.656.0 release #6503

Closed
3 of 4 tasks
Steuls opened this issue Sep 23, 2024 · 3 comments
Closed
3 of 4 tasks

DynamoDB client url changed after 3.656.0 release #6503

Steuls opened this issue Sep 23, 2024 · 3 comments
Assignees
Labels
bug This issue is a bug. p2 This is a standard priority issue response-requested Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.

Comments

@Steuls
Copy link

Steuls commented Sep 23, 2024

Checkboxes for prior research

Describe the bug

With the latest version of the SDK the URL the dynamo requests go to has changed, this has caused us issues since all our applications live in a whitelisted networking space and so suddenly went down. This change to use the accountId URL should be a separate flag as otherwise this is a breaking change

Regression Issue

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

SDK version number

3.656.0

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

18

Reproduction Steps

Load previous version and the output URL is the generic one
Load current version and the output URL is the AccountId specific one

Observed Behavior

The URL requests are now being sent to the new URL

Expected Behavior

The URL requests are being sent to should not be changed from the original default behaviour

Possible Solution

Set this new setting as a flag

Additional Information/Context

No response

@Steuls Steuls added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Sep 23, 2024
@siddsriv
Copy link
Contributor

siddsriv commented Sep 23, 2024

hi,

there's a flag called accountIdEndpointMode for account-based endpoints that defaults to preferred.

you can set this to disabled if you don't want to utilize account-based endpoints.

details here: https://docs.aws.amazon.com/sdkref/latest/guide/feature-account-endpoints.html

@aBurmeseDev aBurmeseDev added response-requested Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days. p2 This is a standard priority issue and removed needs-triage This issue or PR still needs to be triaged. labels Sep 23, 2024
@Steuls
Copy link
Author

Steuls commented Sep 24, 2024

Thanks for that information. It should be noted though that the page you linked says support for the V3 SDK is not supported so does have conflicting information. Also doesn't change the fact this is more of a breaking change since it is directly changing the functionality from the version before?

@aBurmeseDev aBurmeseDev self-assigned this Sep 24, 2024
@aBurmeseDev aBurmeseDev added investigating Issue is being investigated and/or work is in progress to resolve the issue. and removed response-requested Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days. labels Sep 24, 2024
@aBurmeseDev
Copy link
Member

Thanks for your patience @Steuls. Please refer to this announcement here:

In AWS SDK for JavaScript v3.656.0, we released changes to the DynamoDB client that adopt a new AWS account-based endpoints feature. For more information on account based endpoints, please refer to the official SDK documentation. In SDK releases from this version on, clients will connect to a DynamoDB endpoint in the form of (account-id).ddb.(region).amazonaws.com instead of dynamodb.(region).amazonaws.com.

If your network configuration blocks outgoing traffic to DynamoDB based on DNS names or endpoint URLs, you must adjust your configuration, because the service's DNS name will change. You may also choose to switch to an IP-based configuration. The IP address ranges for DynamoDB, as well as other AWS services, can be found in the AWS documentation.

You may instead disable account-based endpoints for DynamoDB by setting the config flag accountIdEndpointMode to disabled. We recommend against this because the DynamoDB service uses account-based endpoints to ensure performance and scalability.

Here's updated docs for reference: https://docs.aws.amazon.com/sdkref/latest/guide/feature-account-endpoints.html

Apologies for the inconvenience and feel free to let us know if there are any further questions.

@aBurmeseDev aBurmeseDev added response-requested Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days. and removed investigating Issue is being investigated and/or work is in progress to resolve the issue. labels Sep 25, 2024
@Steuls Steuls closed this as completed Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. p2 This is a standard priority issue response-requested Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.
Projects
None yet
Development

No branches or pull requests

3 participants