A company has an application running on Amazon EC2 instances in a private subnet that connects to a third-party service provider's public HTTP endpoint through a NAT gateway. As request rates increase, new connections are starting to fail. At the same time, the ErrorPortAllocation Amazon CloudWatch metric count for the NAT gateway is increasing. Which of the following actions should improve the connectivity issues? (Choose two.)
Select an option, then click Submit answer.
Reference / correct answer:
Create additional NAT gateways in the public subnet and split client instances into multiple private subnets, each with a route to a different NAT gateway.
Most accepted answer: E. Create additional NAT gateways in the public subnet and split client instances into multiple private subnets, each with a route to a different NAT gateway.
Community votes: A=1, B=1, C=2, E=4
C, and E. https://aws.amazon.com/premiumsupport/knowledge-center/vpc-resolve-port-allocation-errors/ Limit the number of connections that clients can make to a single destination. Keeplive reduce the number of new connection establish. upvoted 16 times
The issue with D is that you still only have ONE private subnet which has ONE route table. Having multiple default routes in a single route table won't work. Therefore, I will go with C and E. upvoted 9 times Ishu_awsguy 4 years, 9 months ago It doesnt really mention it. the language is update the private route table, there an be multiple in the backend upvoted 1 times Ishu_awsguy 4 years, 9 months ago the question information isnt too good. C is also right. So may be ill go with C and E. upvoted 1 times ... ...
It doesnt really mention it. the language is update the private route table, there an be multiple in the backend upvoted 1 times Ishu_awsguy 4 years, 9 months ago the question information isnt too good. C is also right. So may be ill go with C and E. upvoted 1 times ...
the question information isnt too good. C is also right. So may be ill go with C and E. upvoted 1 times
Selected Answer: AE From here: https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html 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. upvoted 1 times