AWS Certified Solutions Architect - Associate free question 4 / 10 · Domain 2: Design Resilient Architectures
A company receives files from its business partners on an SFTP server that runs on a single EC2 instance. When this server stops, receiving stops. The company does not want its partners to change the SFTP client settings. It wants to raise the availability of receiving files and also eliminate the work of looking after the server's operating system and software. The received files are stored in S3. What should it do?
- Move to a Transfer Family web app with S3 as the storage, and receive the partners' SFTP client connections on the web app as well
- Place an S3 File Gateway with S3 as the storage, receive the partners' SFTP connections on the gateway, and have them send to it with their current settings
- Place the SFTP server EC2 instances in an Auto Scaling group across multiple Availability Zones, and leave operating system and software updates to a regular patching process
- Move to a Transfer Family SFTP server endpoint with S3 as the storage, and point the current host name at the endpoint
Show the answer and explanation
Answer: D
Why this is correct
Transfer Family is a fully managed service that exchanges files over SFTP, FTPS, FTP, and AS2, and through a browser, directly with S3 or EFS. The guide says that you can use servers that speak file transfer protocols without running server infrastructure, and that you can migrate while keeping your users' clients and configurations. For a server, you associate your host name with the server endpoint and then add users. The infrastructure spans up to 3 Availability Zones, and a redundant fleet that scales automatically handles connection and transfer requests. This removes both the weakness that receiving stops when one EC2 instance stops and the work of looking after the operating system and software.
Why the other options are wrong
"Place the SFTP server EC2 instances in an Auto Scaling group across multiple Availability Zones, and leave operating system and software updates to a regular patching process" … Placing instances in multiple Availability Zones lets the setup survive a single failure, but you are still running EC2 instances with SFTP software on your own. Rebuilding AMIs and managing the software configuration remain. The guide contrasts this with Transfer Family, where you do not need to run the file transfer server infrastructure.
"Place an S3 File Gateway with S3 as the storage, receive the partners' SFTP connections on the gateway, and have them send to it with their current settings" … S3 File Gateway is a gateway that presents S3 as an NFS or SMB file share. It has no front end that accepts SFTP connections, so the partners' SFTP clients cannot send to it. To send, the partners would have to change how they connect.
"Move to a Transfer Family web app with S3 as the storage, and receive the partners' SFTP client connections on the web app as well" … A Transfer Family web app is a managed web interface for working with S3 data from a browser. It is for letting business users use S3 in a browser, and it is not a front end that accepts connections from SFTP clients. The partners would have to switch to working in a browser, and could not send with their current settings.
Key point
The strength of Transfer Family is that you can remove the server on your side without changing anything on the other side. The received files go into S3, so later processing and analytics can be connected with AWS services. You choose S3 or EFS for storage; the examples are S3 for gathering third-party uploads into a data lake and EFS when you want to treat the data as a file system. Within the same service, a web app that you use in a browser and a server endpoint that speaks a protocol have different roles.