AWS AmazonRDS documentation change
Summary
Updated Oracle restore documentation to include Secrets Manager integration for master passwords
Security assessment
Documents the option to use Secrets Manager for password management during point-in-time restores, improving security practices but not addressing a specific vulnerability.
Diff
diff --git a/AmazonRDS/latest/UserGuide/USER_PIT.md b/AmazonRDS/latest/UserGuide/USER_PIT.md index 8c3587374..11308eb7a 100644 --- a//AmazonRDS/latest/UserGuide/USER_PIT.md +++ b//AmazonRDS/latest/UserGuide/USER_PIT.md @@ -27 +27 @@ For information about restoring a DB instance with an RDS Extended Support versi -Some of the database engines used by Amazon RDS have special considerations when restoring from a point in time: +Some Amazon RDS database engines have special considerations when restoring from a point in time: @@ -35 +35 @@ With the Db2 license through AWS Marketplace model, you need an active AWS Marke - * When you restore an Oracle DB instance to a point in time, you can specify a different Oracle DB engine, license model, and DBName (SID) to be used by the new DB instance. + * When you restore an RDS for Oracle DB instance to a point in time, you can specify a different DB engine, license model, and DBName (SID) for the restored DB instance. You can also specify that RDS should store manage master user passwords in AWS Secrets Manager. For more information, see [Overview of managing master user passwords with AWS Secrets Manager](./rds-secrets-manager.html#rds-secrets-manager-overview).