-
Notifications
You must be signed in to change notification settings - Fork 587
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
Comments
hi, there's a flag called you can set this to details here: https://docs.aws.amazon.com/sdkref/latest/guide/feature-account-endpoints.html |
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? |
Thanks for your patience @Steuls. Please refer to this announcement here:
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. |
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. |
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
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
The text was updated successfully, but these errors were encountered: