Which solution will meet these requirements with the LEAST operational overhead?
Migrate to Amazon CloudWatch dashboards. Recreate the dashboards to match the existing Grafana dashboards. Use automatic dashboards where possible.
Create an Amazon Managed Grafana workspace. Configure a new Amazon CloudWatch data source. Export dashboards from the existing Grafana instance. Import the dashboards into the new workspace.
Create an AMI that has Grafana pre-installed. Store the existing dashboards in Amazon Elastic File System (Amazon EFS). Create an Auto Scaling group that uses the new AMI. Set the Auto Scaling group’s minimum, desired, and maximum number of instances to one. Create an Application Load Balancer that serves at least two Availability Zones.
Configure AWS Backup to back up the EC2 instance that runs Grafana once each hour. Restore the EC2 instance from the most recent snapshot in an alternate Availability Zone when required.
Explanations:
Migrating to Amazon CloudWatch dashboards requires recreating the existing Grafana dashboards, which involves significant manual effort and does not guarantee high availability in under 10 minutes.
Creating an Amazon Managed Grafana workspace allows for easy management and scaling. By exporting and importing dashboards, the existing work can be preserved, and AWS handles the underlying infrastructure, minimizing operational overhead.
Although creating an AMI and using Auto Scaling provides high availability, managing the EC2 instances and scaling adds operational complexity, which goes against the requirement to minimize ongoing maintenance.
While AWS Backup can provide a way to restore the instance, the recovery time from snapshots can exceed 10 minutes, making it unsuitable for the requirement of minimal downtime.
I appraise that the answer is:
Create an Amazon Managed Grafana workspace. Configure a new Amazon CloudWatch data source. Export dashboards from the existing Grafana instance. Import the dashboards into the new workspace.