Migrate dynamodb engine to AWS SDK v2 #50250
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GavinFrazar
added
the
no-changelog
github-actions
bot
added
database-access
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
GavinFrazar
added
aws
This migrates the Database Service engine for DynamoDB to use AWS SDK v2. FIPS endpoint resolution has also been enabled. Finally, the engine will now resolve to the AWS-account-based endpoint for DynamoDB operations in supported regions.
GavinFrazar
force-pushed
the
gavinfrazar/migrate-dynamodb-engine-sdk
branch
from
a036fa2 to
b113763
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changelog: Teleport Database Service will now resolve DynamoDB endpoints to AWS-account-based endpoints in supported regions.
Part of #14142
This migrates the Database Service engine for DynamoDB to use AWS SDK v2.
FIPS endpoint resolution has also been enabled.
Finally, if the AWS account ID is known1 then the engine will resolve to the account ID based endpoint for DynamoDB operations in supported regions.
Footnotes
I think it was always a required
dbspec field, but it's trivial to handle the case where it isn't, because that was prior behavior anyway ↩