Which solution will meet these requirements with the LEAST operational overhead?
Create an AWS Transfer Family server. Configure an internet-facing VPC endpoint for the Transfer Family server. Specify an Elastic IP address for each subnet. Configure the Transfer Family server to place files into an Amazon Elastic File System (Amazon EFS) file system that is deployed across multiple Availability Zones. Modify the configuration on the downstream applications that access the existing NFS share to mount the EFS endpoint instead.
Create an AWS Transfer Family server. Configure a publicly accessible endpoint for the Transfer Family server. Configure the Transfer Family server to place files into an Amazon Elastic File System (Amazon EFS) file system that is deployed across multiple Availability Zones. Modify the configuration on the downstream applications that access the existing NFS share to mount the EFS endpoint instead.
Use AWS Application Migration Service to migrate the existing Linux VM to an Amazon EC2 instance. Assign an Elastic IP address to the EC2 instance. Mount an Amazon Elastic File System (Amazon EFS) file system to the EC2 instance. Configure the SFTP server to place files in the EFS file system. Modify the configuration on the downstream applications that access the existing NFS share to mount the EFS endpoint instead.
Use AWS Application Migration Service to migrate the existing Linux VM to an AWS Transfer Family server. Configure a publicly accessible endpoint for the Transfer Family server. Configure the Transfer Family server to place files into an Amazon FSx for Lustre file system that is deployed across multiple Availability Zones. Modify the configuration on the downstream applications that access the existing NFS share to mount the FSx for Lustre endpoint instead.
Explanations:
This option uses AWS Transfer Family to provide SFTP capabilities and specifies an internet-facing VPC endpoint with Elastic IPs, ensuring static IP addresses for external vendors. It also utilizes Amazon EFS across multiple Availability Zones for high availability, meeting the requirement with minimal operational overhead.
While this option correctly uses AWS Transfer Family and Amazon EFS for high availability, it does not provide static public IP addresses for external vendors, which is a key requirement. The publicly accessible endpoint could lead to dynamic IP changes, which doesn’t satisfy the vendor’s need for static IPs.
This option involves migrating the Linux VM to an EC2 instance and assigning an Elastic IP address. However, this increases operational overhead compared to using AWS Transfer Family and does not offer built-in high availability as effectively. It also does not utilize AWS-managed services for SFTP, which are designed for ease of use and scalability.
This option incorrectly suggests using AWS Application Migration Service to migrate the existing VM to an AWS Transfer Family server, which is not possible. AWS Transfer Family is a service, not a target for migration. Additionally, FSx for Lustre is not necessary for this scenario; Amazon EFS would suffice.
I figure that the answer is:
Create an AWS Transfer Family server. Configure an internet-facing VPC endpoint for the Transfer Family server. Specify an Elastic IP address for each subnet. Configure the Transfer Family server to place files into an Amazon Elastic File System (Amazon EFS) file system that is deployed across multiple Availability Zones. Modify the configuration on the downstream applications that access the existing NFS share to mount the EFS endpoint instead.