What should a solutions architect do to improve the reliability and scalability of the SFTP solution?
Move the EC2 instance into an Auto Scaling group. Place the EC2 instance behind an Application Load Balancer (ALB). Update the DNS record sftp.example.com in Route 53 to point to the ALB.
Migrate the SFTP server to AWS Transfer for SFTP. Update the DNS record sftp.example.com in Route 53 to point to the server endpoint hostname.
Migrate the SFTP server to a file gateway in AWS Storage Gateway. Update the DNS record sftp.example.com in Route 53 to point to the file gateway endpoint.
Place the EC2 instance behind a Network Load Balancer (NLB). Update the DNS record sftp.example.com in Route 53 to point to the NLB.
Explanations:
While using an Auto Scaling group and an Application Load Balancer (ALB) can enhance reliability, ALBs are not typically used for SFTP traffic, which requires TCP.
AWS Transfer for SFTP is a fully managed service that improves the reliability and scalability of SFTP, and updating the DNS record to point to the service is correct.
AWS Storage Gateway’s file gateway is not designed for SFTP services and does not handle SFTP connections, making this option inappropriate for the given scenario.
A Network Load Balancer (NLB) could support TCP traffic, but without auto-scaling capabilities and direct management of SFTP, it is less optimal than AWS Transfer for SFTP.