AWS AmazonRDS high security documentation change
Summary
Added same KMS encryption key access events (RDS-EVENT-0420, 0418, 0419) and maintenance event as Aurora version
Security assessment
Identical to Aurora changes - documents encryption key access failures impacting database availability, which is security-relevant for data protection.
Diff
diff --git a/AmazonRDS/latest/UserGuide/USER_Events.Messages.md b/AmazonRDS/latest/UserGuide/USER_Events.Messages.md index 47df63b64..1e4f0a9fd 100644 --- a/AmazonRDS/latest/UserGuide/USER_Events.Messages.md +++ b/AmazonRDS/latest/UserGuide/USER_Events.Messages.md @@ -93,0 +94 @@ availability | RDS-EVENT-0396 | Amazon RDS has scheduled a reboot for this read +availability | RDS-EVENT-0420 | Amazon RDS has been unable to access the KMS encryption key for database instance `name`. This database will be placed into an inaccessible state. Please refer to the troubleshooting section in the Amazon RDS documentation for further details. | None @@ -160,0 +162,2 @@ failure | RDS-EVENT-0356 | RDS was unable to configure the Kerberos endpoint in +failure | RDS-EVENT-0418 | Amazon RDS is unable to access the KMS encryption key for database instance `name`. This is likely due to the key being disabled or Amazon RDS being unable to access it. If this continues the database will be placed into an inaccessible state. Please refer to the troubleshooting section in the Amazon RDS documentation for further details. | None +failure | RDS-EVENT-0419 | Amazon RDS can now successfully access the KMS encryption key for database instance `name`. | None @@ -177,0 +181 @@ maintenance | RDS-EVENT-0399 | Waiting for the DB engine version upgrade to fin +maintenance | RDS-EVENT-0422 | RDS will replace the host of DB instance `name` due to a pending maintenance action. | None