Support for storing master user password in Secrets Manager

[adammichalik]

Copied from the provider issue hashicorp/terraform-provider-aws#28538, supported since provider ver. 4.61.0:

Amazon RDS now supports integration with AWS Secrets Manager to streamline how you manage your master user password for your RDS database instances. With this feature, RDS fully manages the master user password and stores it in AWS Secrets Manager whenever your RDS database instances are created, modified, or restored. The new feature supports the entire lifecycle maintenance for your RDS master user password including regular and automatic password rotations; removing the need for you to manage rotations using custom Lambda functions.

RDS integration with AWS Secrets Manager improves your database security by ensuring your RDS master user password is not visible in plaintext to administrators or engineers during your database creation workflow. Furthermore, you have flexibility in encrypting the secrets using your own managed key or by using a KMS key provided by AWS Secrets Manager. RDS and AWS Secrets Manager provide you the ease and security in managing your master user password for your database instances, relieving you from complex credential management activities such as setting up custom Lambda functions to manage password rotations.

This is a great improvement from the security perspective, I would love to see it propagated to this module.

[sptdevos]

+1

[ishwar-amzn]

@adammichalik @sptdevos I am starting working on this request.

[lnkrishnan]

+1

[gruckion]

@adammichalik @sptdevos I am starting working on this request.

How you getting on?

[terry-wade-cko]

+1

[mbacchi]

@ishwar-amzn I was coming here to request support for the manage_master_user_password feature that was recently released in the AWS provider v4.61.0 [0]. Will your support for secrets manager also comprise that feature or should I open another Github Issue to handle that feature request?

[rlmartin]

+1

[yannickvr]

There's a PR already open #489 which solves this. Would be nice to get this somewhere soon!

[github-actions]

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

[rlmartin]

Any progress on this?

[antonbabenko]

This issue has been resolved in version 6.0.0 🎉

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.