AWS transfer documentation change
Summary
Restructured availability zone redundancy documentation and added explicit recommendation for multi-AZ VPC deployments
Security assessment
While the changes improve documentation around high availability and fault tolerance, they focus on operational resilience rather than addressing specific security vulnerabilities or introducing security features.
Diff
diff --git a/transfer/latest/userguide/disaster-recovery-resiliency.md b/transfer/latest/userguide/disaster-recovery-resiliency.md index 7c279080f..6d3fcf3a5 100644 --- a//transfer/latest/userguide/disaster-recovery-resiliency.md +++ b//transfer/latest/userguide/disaster-recovery-resiliency.md @@ -11 +11 @@ AWS Transfer Family supports up to 3 Availability Zones and is backed by an auto -Note the following: +For all Transfer Family endpoints: @@ -13,3 +13 @@ Note the following: - * For public endpoints: - - * Availability Zone-level redundancy is built into the service + * Availability Zone-level redundancy is built into the service. @@ -19 +17,2 @@ Note the following: - * This redundancy is provided automatically + * This redundancy is provided automatically. + @@ -21 +19,0 @@ Note the following: - * For endpoints in a Virtual Private Cloud (VPC), see [Create a server in a virtual private cloud](./create-server-in-vpc.html). @@ -23,0 +22 @@ Note the following: +###### Note @@ -24,0 +24 @@ Note the following: +For endpoints in a Virtual Private Cloud (VPC), it is possible to provide a single subnet. However, we recommend that you create endpoints in multiple availability zones within your VPC, to reduce the risk of service disruptions during Availability Zone outages. @@ -27,0 +28,2 @@ See also + * For details on how to create Transfer Family servers in a VPC, see [Create a server in a virtual private cloud](./create-server-in-vpc.html). +