Which solution will meet these requirements?
Create an AMI of the existing EC2 instance. Create an Auto Scaling group of EC2 instances behind an Application Load Balancer. Configure the Auto Scaling group to have a minimum of three instances.
Use AWS Transfer Family to create an FTP server that places the files in Amazon Elastic File System (Amazon EFS). Mount the EFS volume to the existing EC2 instance. Point the EC2 instance to the new path for file processing.
Use AWS Transfer Family to create an FTP server that places the files in Amazon S3. Use an S3 event notification through Amazon Simple Notification Service (Amazon SNS) to invoke an AWS Lambda function. Configure the Lambda function to add the metadata and update the delivery system.
Update the handheld devices to place the files directly in Amazon S3. Use an S3 event notification through Amazon Simple Queue Service (Amazon SQS) to invoke an AWS Lambda function. Configure the Lambda function to add the metadata and update the delivery system.
Explanations:
While creating an AMI and using an Auto Scaling group could improve availability, it does not address the core issue of the FTP server’s dropped connections and memory problems. It also does not ensure that files are reliably archived in S3 or that metadata is updated.
Using AWS Transfer Family with EFS would not resolve the fundamental issues of connectivity and data loss since the EC2 instance would still rely on FTP. This option does not guarantee that the delivery system is always updated or that all files are archived.
This option leverages AWS Transfer Family to create a robust FTP server that directly places files in S3, eliminating the memory and connection issues of the EC2 instance. The use of S3 event notifications allows for real-time processing of files, ensuring that metadata is added and the delivery system is updated efficiently.
This option cannot be implemented as stated, since the problem specifies that the handheld devices cannot be modified. Additionally, placing files directly in S3 and using SQS does not solve the immediate FTP connection and archiving issues in the current setup.