feat(graphql-model-transformer): add dsql support for sql lambda #3117
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.
Description of changes
This PR introduces IAM-based authentication support for DSQL database connections in SQL lambda, enhancing our current authentication capabilities.
The implementation leverages existing SSM parameter to store the connection string, following our existing credential storage strategy for Gen2 brownfield support. Connection strings will follow the format
postgres://hostname:port/database
, with DSQL hosts identified by the*.dsql.*.on.aws
domain pattern.Authentication will use the default
admin
user, with database credentials dynamically generated usingDsqlSigner
helper methods provided by the SDK. This approach provides a flexible and secure method for establishing database connections while maintaining our infrastructure's existing patterns.Key Changes
CDK / CloudFormation Parameters Changed
NA
Issue #, if available
NA
Description of how you validated changes
Checklist
yarn test
passesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.