Which solution will meet these requirements?
Use AWS Transfer Family to configure an SFTP-enabled server with a publicly accessible endpoint. Choose the S3 data lake as the destination.
Use Amazon S3 File Gateway as an SFTP server. Expose the S3 File Gateway endpoint URL to the new partner. Share the S3 File Gateway endpoint with the new partner.
Launch an Amazon EC2 instance in a private subnet in a VPC. Instruct the new partner to upload files to the EC2 instance by using a VPN. Run a cron job script on the EC2 instance to upload files to the S3 data lake.
Launch Amazon EC2 instances in a private subnet in a VPC. Place a Network Load Balancer (NLB) in front of the EC2 instances. Create an SFTP listener port for the NLB. Share the NLB hostname with the new partner. Run a cron job script on the EC2 instances to upload files to the S3 data lake.
Explanations:
AWS Transfer Family provides a fully managed SFTP service, which can directly integrate with S3, offering high availability and minimal operational overhead.
Amazon S3 File Gateway does not support SFTP directly and cannot be used as an SFTP server, making it unsuitable for this requirement.
Using an EC2 instance with VPN and cron jobs requires more operational overhead and does not ensure high availability or scalability for SFTP connections.
Setting up EC2 instances with an NLB for SFTP requires custom setup, lacks managed service benefits, increases operational burden, and does not minimize overhead.
If I’m correct, the answer is:
Use AWS Transfer Family to configure an SFTP-enabled server with a publicly accessible endpoint. Choose the S3 data lake as the destination.
I compute that the answer is:
Use AWS Transfer Family to configure an SFTP-enabled server with a publicly accessible endpoint. Choose the S3 data lake as the destination.