How can this be achieved?
Create hourly snapshots of the production RDS DB instance.
Create a Multi-AZ RDS Read Replica of the production RDS DB instance.
Create multiple RDS Read Replicas of the production RDS DB instance. Place the Read Replicas in an Auto Scaling group.
Create a Single-AZ RDS Read Replica of the production RDS DB instance. Create a second Single-AZ RDS Read Replica from the replica.
Explanations:
Creating hourly snapshots only provides backup functionality. It does not support real-time reporting or high availability for the reporting tool.
A Multi-AZ RDS Read Replica provides high availability and can be used for reporting without impacting the production database. It replicates data asynchronously and is designed for read-heavy workloads.
While RDS Read Replicas are used for scaling read operations, placing them in an Auto Scaling group is not necessary for the reporting tool, and it doesn’t ensure high availability or prevent performance impact on the production application.
A Single-AZ Read Replica lacks high availability. Creating another Single-AZ Read Replica from the replica doesn’t improve fault tolerance or ensure high availability.
If memory serves me right, the answer is:
Create a Multi-AZ RDS Read Replica of the production RDS DB instance.