AWS fsx documentation change
Summary
Changed formatting of 'EndpointIpAddressRange' parameter references to lowercase 'endpoint IP address range' and removed code formatting/bolding in multiple sections
Security assessment
The changes are purely stylistic/documentation formatting adjustments (changing parameter name formatting to plain text). There is no indication of security vulnerability fixes, security configuration changes, or new security guidance. The content remains technically identical regarding routing requirements.
Diff
diff --git a/fsx/latest/OpenZFSGuide/access-within-aws.md b/fsx/latest/OpenZFSGuide/access-within-aws.md index 632fb2b74..9f07be3c4 100644 --- a//fsx/latest/OpenZFSGuide/access-within-aws.md +++ b//fsx/latest/OpenZFSGuide/access-within-aws.md @@ -50 +50 @@ Only [AWS Transit Gateway](https://aws.amazon.com/transit-gateway/?whats-new-car -When you access your Multi-AZ file system from outside of the file system's VPC, FSx for OpenZFS will manage routing configurations as long as the file system's `EndpointIpAddressRange` is within the CIDR range of the file system's VPC and does not overlap with the CIDR range of any subnets in the VPC. However, if you access your Multi-AZ file system from outside of the file system's VPC, and the file system's `EndpointIpAddressRange` is outside of the CIDR range of the file system's VPC, you will need to set up additional routing in Transit Gateway. For information on how to configure Transit Gateway to access your FSx for OpenZFS file system, see Configuring routing using AWS Transit Gateway. +When you access your Multi-AZ file system from outside of the file system's VPC, FSx for OpenZFS will manage routing configurations as long as the file system's endpoint IP address range is within the CIDR range of the file system's VPC and does not overlap with the CIDR range of any subnets in the VPC. However, if you access your Multi-AZ file system from outside of the file system's VPC, and the file system's endpoint IP address range is outside of the CIDR range of the file system's VPC, you will need to set up additional routing in Transit Gateway. For information on how to configure Transit Gateway to access your FSx for OpenZFS file system, see Configuring routing using AWS Transit Gateway. @@ -62 +62 @@ Ensure that all of the route tables you're using are associated with your Multi- -If you have a Multi-AZ file system with an `EndpointIPAddressRange` that's outside your VPC's CIDR range, you need to set up additional routing in your AWS Transit Gateway to access your file system from peered or on-premises networks. No additional Transit Gateway configuration is required for Single-AZ file systems or Multi-AZ file systems with an `EndpointIPAddressRange` that's within your VPC's IP address range. +If you have a Multi-AZ file system with an endpoint IP address range that's outside your VPC's CIDR range, you need to set up additional routing in your AWS Transit Gateway to access your file system from peered or on-premises networks. No additional Transit Gateway configuration is required for Single-AZ file systems or Multi-AZ file systems with an endpoint IP address range that's within your VPC's IP address range. @@ -74 +74 @@ To access a Multi-AZ file system using a Transit Gateway, each of the Transit Ga - 3. In **Network & security** copy the **Endpoint IP address range**. + 3. In **Network & security** copy the endpoint IP address range.