Which of the following actions would allow the database to handle the month-end load with the LEAST impact on performance?
Pre-warming Elastic Load Balancers, using a bigger instance type, changing all Amazon EBS volumes to GP2 volumes.
Performing a one-time migration of the database cluster to Amazon RDS, and creating several additional read replicas to handle the load during end of month.
Using Amazon CloudWatch with AWS Lambda to change the type, size, or IOPS of Amazon EBS volumes in the cluster based on a specific CloudWatch metric.
Replacing all existing Amazon EBS volumes with new PIOPS volumes that have the maximum available storage size and I/O per second by taking snapshots before the end of the month and reverting back afterwards.
Explanations:
Pre-warming Elastic Load Balancers is useful for performance but does not directly address the database’s I/O issues. Using a bigger instance type may help with compute resources, but simply changing to GP2 volumes does not guarantee better performance for heavy I/O operations compared to other options.
Migrating to Amazon RDS allows for managed database services that can automatically scale to handle increased load. Creating read replicas helps distribute the read traffic, which is particularly beneficial during peak reporting times, thus alleviating pressure on the primary database instance.
While using CloudWatch with Lambda for dynamic changes to EBS volumes can be beneficial, it requires time for the changes to take effect and might not be instant. Additionally, changing EBS types or IOPS dynamically may not address immediate performance degradation during month-end load spikes.
Replacing EBS volumes with PIOPS volumes could improve performance, but the method of taking snapshots and reverting back introduces downtime and complexity. This approach may not provide the immediate performance boost needed during peak reporting periods.