Which solution meets these requirements?
Register the customer-owned block of IP addresses in the company’s AWS account. Create Elastic IP addresses from the address pool and assign them to an AWS Transfer for SFTP endpoint. Use AWS Transfer to store the files in Amazon S3.
Add a subnet containing the customer-owned block of IP addresses to a VPC. Create Elastic IP addresses from the address pool and assign them to an Application Load Balancer (ALB). Launch EC2 instances hosting FTP services in an Auto Scaling group behind the ALB. Store the files in attached Amazon Elastic Block Store (Amazon EBS) volumes.
Register the customer-owned block of IP addresses with Amazon Route 53. Create alias records in Route 53 that point to a Network Load Balancer (NLB). Launch EC2 instances hosting FTP services in an Auto Scaling group behind the NLB. Store the files in Amazon S3.
Register the customer-owned block of IP addresses in the company’s AWS account. Create Elastic IP addresses from the address pool and assign them to an Amazon S3 VPC endpoint. Enable SFTP support on the S3 bucket.
Explanations:
This option allows the company to register the customer-owned block of IP addresses and create Elastic IPs to be used with AWS Transfer for SFTP. This service integrates well with Amazon S3 for storage, reducing operational overhead and maintaining static IP addresses for customer firewall allow listing.
While this option involves creating a VPC and using Elastic IPs with an ALB for FTP services, it does not provide a direct SFTP solution. Additionally, it requires managing EC2 instances and EBS volumes, which increases operational overhead instead of decreasing it.
This option does not directly address the SFTP requirement and focuses on FTP instead. While it involves registering IP addresses and creating an NLB, it still requires managing EC2 instances and using EBS for storage, which is more complex than using AWS Transfer for SFTP.
This option suggests creating a VPC endpoint for S3 with Elastic IPs, but S3 does not support SFTP directly. Additionally, the solution does not meet the requirement of providing static IPs for customer firewall configurations since it does not utilize AWS Transfer for SFTP, making it unsuitable.
I map out that the answer is:
Register the customer-owned block of IP addresses in the company’s AWS account. Create Elastic IP addresses from the address pool and assign them to an AWS Transfer for SFTP endpoint. Use AWS Transfer to store the files in Amazon S3.