AWS AmazonRDS medium security documentation change
Summary
Added explicit warning about modifying storage through EC2/EBS consoles/APIs and consequences of unsupported configurations. Removed redundant warning and expanded consequences list.
Security assessment
The change explicitly warns about potential system instability (HA failover failures, replication breaks, redundancy failures) caused by improper storage modifications. This addresses availability and configuration integrity risks that could lead to security-relevant system failures.
Diff
diff --git a/AmazonRDS/latest/UserGuide/custom-managing-sqlserver.storage-modify.md b/AmazonRDS/latest/UserGuide/custom-managing-sqlserver.storage-modify.md index 08885a881..e094f4665 100644 --- a//AmazonRDS/latest/UserGuide/custom-managing-sqlserver.storage-modify.md +++ b//AmazonRDS/latest/UserGuide/custom-managing-sqlserver.storage-modify.md @@ -34,2 +33,0 @@ For more information, see [RDS Custom support perimeter](./custom-concept.html#c - * Modify storage only through the Amazon RDS console or AWS CLI. Modifying storage directly from Amazon EC2 or Amazon EBS console or CLI can cause a mismatch between expected and actual storage settings. For Multi-AZ instances, this can result in mismatched volume sizes on the two hosts, leading to an _unsupported configuration_ state for RDS Custom. - @@ -42,0 +41,17 @@ For general information about storage modification, see [Working with storage fo +###### Important + +Do not modify storage for your RDS Custom for SQL Server DB instance using Amazon EC2 or Amazon EBS consoles or APIs. Direct storage modifications outside of Amazon RDS console or APIs result in an `unsupported-configuration` state for your database. + +When you make direct storage changes using Amazon EC2 or Amazon EBS, Amazon RDS cannot track or manage your database instance state. This might cause: + + * High availability failover mechanisms from functioning correctly + + * Database replication setups to break + + * Redundancy features to fail + + + + +Modify storage only through Amazon RDS console or APIs to keep your database in a supported state. See [Fixing unsupported configurations in RDS Custom for SQL Server](./custom-troubleshooting-sqlserver.html#custom-troubleshooting-sqlserver.fix-unsupported) for recovery steps. +