You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, just wanted to say how much I appreciate this construct! It saved me MANY hours to automate database management tasks in CDK!
I'd like to share a proposal: add support for enabling IAM Authentication on the Role construct (for clusters that have it enabled), as an alternative to username/password. E.g.:
In this case, Role would either not create a secret, or create one without a password field. Another option (to keep the Role construct simple / consistent) would be to create a separate RoleWithIAM construct.
In practice, the SQL statements in Role and Provider for PostgreSQL and MySQL would have to be amended as per the RDS IAM documentation.
Happy to provide this as a PR for discussion.
The text was updated successfully, but these errors were encountered:
Love it, great idea! I haven't really used IAM, as I was never sure how the permissions really worked, but happy to see a PR. Probably very hard to write a test for I assume? So may need some mocking.
First, just wanted to say how much I appreciate this construct! It saved me MANY hours to automate database management tasks in CDK!
I'd like to share a proposal: add support for enabling IAM Authentication on the
Role
construct (for clusters that have it enabled), as an alternative to username/password. E.g.:In this case,
Role
would either not create a secret, or create one without apassword
field. Another option (to keep theRole
construct simple / consistent) would be to create a separateRoleWithIAM
construct.In practice, the SQL statements in
Role
andProvider
for PostgreSQL and MySQL would have to be amended as per the RDS IAM documentation.Happy to provide this as a PR for discussion.
The text was updated successfully, but these errors were encountered: