AWS managedservices documentation change
Summary
Added opt-out mechanism via specific tag for RDS storage auto-remediation features across multiple alerts
Security assessment
While the change documents a security-adjacent feature (control over automated storage scaling), there's no evidence of addressing a specific vulnerability. The tag-based opt-out introduces a new security control surface but isn't tied to a disclosed security issue.
Diff
diff --git a/managedservices/latest/userguide/auto-remediation.md b/managedservices/latest/userguide/auto-remediation.md index 8cded96be..484014fb4 100644 --- a//managedservices/latest/userguide/auto-remediation.md +++ b//managedservices/latest/userguide/auto-remediation.md @@ -16,2 +16,2 @@ AMSWindowsDiskUsage | When the disk usage of 1 mount point (designated space on -RDS-EVENT-0089 | The DB instance has consumed more than 90% of its allocated storage. | The storage is more than 90% allocated. | AMS automatic remediation first validates that the DB is in a modifiable and available or storage-full state. It then attempts to increase the allocated storage, IOPS, and storage throughput through a CloudFormation changeset. If stack drift is already detected, it falls back to the RDS API to prevent downtime. -RDS-EVENT-0007 | Allocated storage for the DB instance has been exhausted. To resolve, allocate additional storage. | Storage is 100% allocated. | AMS automatic remediation first validates that the DB is in a modifiable and available or storage-full state. It then attempts to increase the allocated storage, IOPS, and storage throughput through a CloudFormation changeset. If stack drift is already detected, it falls back to the RDS API to prevent downtime. +RDS-EVENT-0089 | The DB instance has consumed more than 90% of its allocated storage. | The storage is more than 90% allocated. | AMS automatic remediation first validates that the DB is in a modifiable and available or storage-full state. It then attempts to increase the allocated storage, IOPS, and storage throughput through a CloudFormation changeset. If stack drift is already detected, it falls back to the RDS API to prevent downtime. This feature can be opted out of by adding the following tag to the RDS DB Instance: `"Key: ams:rt:ams-rds-max-allocated-storage-policy, Value: ams-opt-out".` +RDS-EVENT-0007 | Allocated storage for the DB instance has been exhausted. To resolve, allocate additional storage. | Storage is 100% allocated. | AMS automatic remediation first validates that the DB is in a modifiable and available or storage-full state. It then attempts to increase the allocated storage, IOPS, and storage throughput through a CloudFormation changeset. If stack drift is already detected, it falls back to the RDS API to prevent downtime. This feature can be opted out of by adding the following tag to the RDS DB Instance: `"Key: ams:rt:ams-rds-max-allocated-storage-policy, Value: ams-opt-out".` @@ -19 +19 @@ RDS-EVENT-0224 | The requested allocated storage reaches or exceeds the configur -RDS-Storage-Capacity | Less than 1GB is left at the allocated storage for the DB instance. | Storage is 99% allocated. | AMS automatic remediation first validates that the DB is in a modifiable and available or storage-full state. It then attempts to increase the allocated storage, IOPS, and storage throughput through a CloudFormation changeset. If stack drift is already detected, it falls back to the RDS API to prevent downtime. +RDS-Storage-Capacity | Less than 1GB is left at the allocated storage for the DB instance. | Storage is 99% allocated. | AMS automatic remediation first validates that the DB is in a modifiable and available or storage-full state. It then attempts to increase the allocated storage, IOPS, and storage throughput through a CloudFormation changeset. If stack drift is already detected, it falls back to the RDS API to prevent downtime. This feature can be opted out of by adding the following tag to the RDS DB Instance: `"Key: ams:rt:ams-rds-max-allocated-storage-policy, Value: ams-opt-out".`