Topic 1 Question 58
A company recently migrated its Amazon EC2 instances to VPC private subnets to satisfy a security compliance requirement. The EC2 instances now use a NAT gateway for internet access. After the migration, some long-running database queries from private EC2 instances to a publicly accessible third-party database no longer receive responses. The database query logs reveal that the queries successfully completed after 7 minutes but that the client EC2 instances never received the response. Which configuration change should a network engineer implement to resolve this issue?
Configure the NAT gateway timeout to allow connections for up to 600 seconds.
Enable enhanced networking on the client EC2 instances.
Enable TCP keepalive on the client EC2 instances with a value of less than 300 seconds.
Close idle TCP connections through the NAT gateway.
ユーザの投票
コメント(6)
https://docs.aws.amazon.com/vpc/latest/userguide/nat-gateway-troubleshooting.html#nat- gateway- troubleshooting-timeout
It is Option C)
👍 5study_aws12023/03/23C - correct.
When a TCP connection is idle for a long time, it may be terminated by network devices, including the NAT gateway. By enabling TCP keepalive, the client EC2 instances can periodically send packets to the third-party database to indicate that the connection is still active, preventing it from being terminated prematurely.
👍 4zaazanuna2023/03/19- 正解だと思う選択肢: C
See section "Internet connection drops after 350 seconds" from https://docs.aws.amazon.com/vpc/latest/userguide/nat-gateway-troubleshooting.html
👍 3that1guy2023/04/08
シャッフルモード