AWS fsx documentation change
Summary
Added note about temporary I/O pauses and CloudWatch metric unavailability during Multi-AZ failover/failback events.
Security assessment
Clarifies HA behavior but doesn't address security vulnerabilities or document security features. Focuses on availability expectations.
Diff
diff --git a/fsx/latest/OpenZFSGuide/availability-durability.md b/fsx/latest/OpenZFSGuide/availability-durability.md index ab83980d1..c50a34db5 100644 --- a//fsx/latest/OpenZFSGuide/availability-durability.md +++ b//fsx/latest/OpenZFSGuide/availability-durability.md @@ -67 +67 @@ Multi-AZ (HA) file systems will also fail over if an Availability Zone disruptio -When failing over from one file server to another, the new active file server automatically begins serving all file system read and write requests. A failover typically takes less than 60 seconds from the detection of the failure on the active file server to the promotion of the standby file server to active status. Upon completion of the failover, you continue to have access to your data without manual intervention. When the preferred file server is fully recovered and becomes available, Amazon FSx automatically fails back to it, usually in less than 60 seconds. +When failing over from one file server to another, the new active file server automatically begins serving all file system read and write requests. A failover typically takes less than 60 seconds from the detection of the failure on the active file server to the promotion of the standby file server to active status. Upon completion of the failover, you continue to have access to your data without manual intervention. When the preferred file server is fully recovered and becomes available, Amazon FSx automatically fails back to it, usually in less than 60 seconds. During failover and failback, I/O might be briefly paused and Amazon CloudWatch metrics might be temporarily unavailable.