Which solution meets these requirements with the LEAST amount of operational overhead?
Configure AWS DataSync. Replicate the data to Amazon Elastic Block Store (Amazon EBS) volumes. When the on-premises environment is unavailable, use AWS CloudFormation templates to provision Amazon EC2 instances and attach the EBS volumes.
Configure CloudEndure Disaster Recovery. Replicate the data to replication Amazon EC2 instances that are attached to Amazon Elastic Block Store (Amazon EBS) volumes. When the on-premises environment is unavailable, use CloudEndure to launch EC2 instances that use the replicated volumes.
Provision an AWS Storage Gateway file gateway. Replicate the data to an Amazon S3 bucket. When the on-premises environment is unavailable, use AWS Backup to restore the data to Amazon Elastic Block Store (Amazon EBS) volumes and launch Amazon EC2 instances from these EBS volumes.
Provision an Amazon FSx for Windows File Server file system on AWS. Replicate the data to the file system. When the on-premises environment is unavailable, use AWS CloudFormation templates to provision Amazon EC2 instances and use AWS::CloudFormation::Init commands to mount the Amazon FSx file shares.
Explanations:
While AWS DataSync can replicate data to Amazon EBS volumes, it does not provide a seamless solution for launching EC2 instances with minimal operational overhead. The manual provisioning of instances using CloudFormation templates adds operational complexity and is not ideal for meeting the RPO of 5 minutes.
CloudEndure Disaster Recovery is designed specifically for scenarios like this, allowing near real-time replication of VMs to AWS with minimal downtime. It automates the launch of EC2 instances using the replicated volumes, ensuring that the RPO of 5 minutes is met with minimal operational overhead.
An AWS Storage Gateway file gateway replicates data to S3, which then requires additional steps to restore data to EBS volumes and launch EC2 instances. This introduces more operational overhead and does not meet the 5-minute RPO effectively due to the restore process.
Although provisioning Amazon FSx for Windows File Server allows for data replication, it requires additional operational steps to provision EC2 instances and mount the file shares using CloudFormation. This adds unnecessary complexity and does not align with the goal of minimal operational overhead while ensuring a 5-minute RPO.
As I see it, the answer is:
Configure CloudEndure Disaster Recovery. Replicate the data to replication Amazon EC2 instances that are attached to Amazon Elastic Block Store (Amazon EBS) volumes. When the on-premises environment is unavailable, use CloudEndure to launch EC2 instances that use the replicated volumes.