AWS managedservices documentation change
Summary
Added documentation for a new auto-remediation feature for FSx for NetApp ONTAP volume capacity utilization, including alert conditions and remediation steps.
Security assessment
This change introduces documentation for a new operational auto-remediation feature focused on storage capacity management. While preventing storage exhaustion can avoid service disruptions, the change itself does not address security vulnerabilities or document security-specific features.
Diff
diff --git a/managedservices/latest/userguide/auto-remediation.md b/managedservices/latest/userguide/auto-remediation.md index ece95ff92..4e7578949 100644 --- a//managedservices/latest/userguide/auto-remediation.md +++ b//managedservices/latest/userguide/auto-remediation.md @@ -5 +5 @@ -Amazon EC2 Broken Secure Channel: Remediation automation noteEC2 status check failure: Remediation automation notesEC2 volume usage remediation automationAmazon RDS low storage event remediation automation +Amazon EC2 Broken Secure Channel: Remediation automation noteEC2 status check failure: Remediation automation notesEC2 volume usage remediation automationAmazon RDS low storage event remediation automationONTAP volume capacity remediation automation @@ -20,0 +21,5 @@ RDS-Storage-Capacity | Less than 1GB is left at the allocated storage for the DB +AMSFSXONTAPVolumeCapacityUtilization | The Amazon FSx for NetApp ONTAP volume has consumed more than the default allocated storage (80%). | FSx for ONTAP Volume Capacity Utilization is greater than 80% for two hours (default value). | AMS automatic remediation first validates that the volume lifecycle state is in a modifiable state, then extends volume size by 10% while verifying against the file system maximum capacity. If the file system lacks sufficient storage capacity for the volume expansion, both the volume and file system are expanded together. This expansion is limited to a maximum of three times within any seven-day period. The maximum storage limit that AMS Automation expands to is 5120 GiB. + +###### Note + +If iSCSI LUN is configured on top of the volume, expand the iSCSI LUN at the operating system level. For more information, see [Why is my FSx for ONTAP LUN in read-only mode?](https://repost.aws/knowledge-center/fsx-ontap-lun-in-read-only-mode) @@ -116,0 +122,17 @@ How AWS Managed Services (AMS) auto-remediation works with Amazon RDS low storag +## ONTAP volume capacity remediation automation + +How AWS Managed Services (AMS) auto-remediation works with ONTAP volume capacity issues: + + * Before extending the volume, the automation validates that the volume lifecycle state is in a modifiable state. + + * The automation extends the volume size by 10% while verifying against the file system maximum capacity. + + * If the file system doesn't have sufficient storage capacity to accommodate the volume expansion, both the volume and file system capacity are expanded. + + * Remediation is limited to no more than three updates within a seven-day period. + + * If iSCSI LUN is configured on top of the volume, you must manually expand the iSCSI LUN at the OS level after the automatic remediation completes. For more information, see [Why is my FSx for ONTAP LUN in read-only mode?](https://repost.aws/knowledge-center/fsx-ontap-lun-in-read-only-mode) + + + +