AWS vpc documentation change
Summary
Capitalization consistency changes (NAT gateway -> NAT Gateway), minor grammatical fixes, and UI navigation text updates
Security assessment
Changes are purely cosmetic (capitalization standardization) and grammatical improvements. No security vulnerabilities, mitigations, or security features are mentioned or addressed.
Diff
diff --git a/vpc/latest/userguide/nat-gateway-working-with.md b/vpc/latest/userguide/nat-gateway-working-with.md index cbdd93435..cd30327b1 100644 --- a/vpc/latest/userguide/nat-gateway-working-with.md +++ b/vpc/latest/userguide/nat-gateway-working-with.md @@ -40 +40 @@ Use the following procedure to create a NAT gateway. - * You can assign up to 8 private IPv4 addresses to your private NAT gateway. This limit is not adjustable. + * You can assign up to 8 private IPv4 addresses to your private NAT Gateway. This limit is not adjustable. @@ -83 +83 @@ When you assign an EIP to a public NAT gateway, the network border group of the -Secondary IPv4 addresses are optional and should be assigned or allocated when your workloads that use a NAT gateway exceed 55,000 concurrent connections to a single destination (the same destination IP, destination port, and protocol). Secondary IPv4 addresses increase the number of available ports, and therefore they increase the limit on the number of concurrent connections that your workloads can establish using a NAT gateway. +Secondary IPv4 addresses are optional and should be assigned or allocated when your workloads that use a NAT Gateway exceed 55,000 concurrent connections to a single destination (the same destination IP, destination port, and protocol). Secondary IPv4 addresses increase the number of available ports, and therefore they increase the limit on the number of concurrent connections that your workloads can establish using a NAT Gateway. @@ -104 +104 @@ If the status of the NAT gateway changes to `Failed`, there was an error during -Each IPv4 address can support up to 55,000 simultaneous connections to each unique destination. A unique destination is identified by a unique combination of destination IP address, the destination port, and protocol (TCP/UDP/ICMP). You can increase this limit by associating up to 8 IPv4 addresses to your NAT gateways (1 primary IPv4 address and 7 secondary IPv4 addresses). You are limited to associating 2 Elastic IP addresses to your public NAT gateway by default. You can increase this limit by requesting a quota adjustment. For more information, see [Elastic IP addresses](./amazon-vpc-limits.html#vpc-limits-eips). +Each IPv4 address can support up to 55,000 simultaneous connections to each unique destination. A unique destination is identified by a unique combination of destination IP address, the destination port, and protocol (TCP/UDP/ICMP). You can increase this limit by associating up to 8 IPv4 addresses to your NAT Gateways (1 primary IPv4 address and 7 secondary IPv4 addresses). You are limited to associating 2 Elastic IP addresses to your public NAT gateway by default. You can increase this limit by requesting a quota adjustment. For more information, see [Elastic IP addresses](./amazon-vpc-limits.html#vpc-limits-eips). @@ -112 +112 @@ You can use the [NAT gateway CloudWatch metrics](./metrics-dimensions-nat-gatewa - * Your NAT gateway can have up to 8 IPv4 addresses associated with it (1 primary IPv4 address and 7 secondary IPv4 addresses). You can assign up to 8 private IPv4 addresses to your private NAT gateway. You are limited to associating 2 Elastic IP addresses to your public NAT gateway by default. You can increase this limit by requesting a quota adjustment. For more information, see [Elastic IP addresses](./amazon-vpc-limits.html#vpc-limits-eips). + * Your NAT gateway can have up to 8 IPv4 addresses associated with it (1 primary IPv4 address and 7 secondary IPv4 addresses). You can assign up to 8 private IPv4 addresses to your private NAT Gateway. You are limited to associating 2 Elastic IP addresses to your public NAT gateway by default. You can increase this limit by requesting a quota adjustment. For more information, see [Elastic IP addresses](./amazon-vpc-limits.html#vpc-limits-eips). @@ -170 +170 @@ Cost allocation tags are supported for NAT gateways. Therefore, you can also use - 2. In the navigation pane, choose **NAT gateways**. + 2. In the navigation pane, choose **NAT Gateways**. @@ -183 +183 @@ Cost allocation tags are supported for NAT gateways. Therefore, you can also use -If you no longer need a NAT gateway, you can delete it. After you delete a NAT gateway, its entry remains visible in the Amazon VPC console for about an hour, after which it's automatically removed. You can't remove this entry yourself. +If you no longer need a NAT gateway, you can delete it. After you delete a NAT gateway, its entry remains visible in the Amazon VPC console for about an hour, after which it's automatically removed. You cannot remove this entry yourself. @@ -191 +191 @@ Deleting a NAT gateway disassociates its Elastic IP address, but does not releas - 2. In the navigation pane, choose **NAT gateways**. + 2. In the navigation pane, choose **NAT Gateways**.