feat: cross-account RDS IAM auth via server_iam_assume_role - #1525
Open
lyupan-cb wants to merge 1 commit into
Open
feat: cross-account RDS IAM auth via server_iam_assume_role#1525lyupan-cb wants to merge 1 commit into
lyupan-cb wants to merge 1 commit into
Conversation
RDS IAM tokens are signed with PgDog's single ambient identity, and RDS IAM auth is evaluated in the database's own AWS account, so a backend in a different account can't be reached today (region can be overridden, but not account). Add an optional per-user `server_iam_assume_role` (an IAM role ARN). When it is set and `server_auth = "rds_iam"`, PgDog assumes that role via STS and signs the auth token with the assumed credentials instead of the ambient identity. - new `server_iam_assume_role` field on the user config, carried onto Address - rds_iam::token assumes the role (aws-config AssumeRoleProvider) when set; otherwise the path is unchanged (ambient identity) - warn when the field is set without `server_auth = "rds_iam"` - backward compatible: unset = current behavior; TokenCache/monitor refresh are unchanged - unit tests for config parsing, Address plumbing, and the assume-role decision (pure, no AWS required)
|
|
lyupan-cb
marked this pull request as ready for review
September 11, 2026 00:51
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
RDS IAM tokens are signed with PgDog's single ambient identity, and RDS IAM auth is evaluated in the database's own AWS account, so a backend in a different account can't be reached today (region can be overridden, but not account).
Add an optional per-user
server_iam_assume_role(an IAM role ARN). When it is set andserver_auth = "rds_iam", PgDog assumes that role via STS and signs the auth token with the assumed credentials instead of the ambient identity.server_iam_assume_rolefield on the user configserver_auth = "rds_iam"