A company has a multi-tier application on EC2 instances in an Auto Scaling group with an Amazon RDS for Oracle database using Oracle-specific PL/SQL. Traffic is increasing, causing the EC2 instances to become overloaded and the RDS instance to run out of storage. The Auto Scaling group has no scaling metrics and only defines a minimum healthy instance count. Traffic will continue increasing at a steady but unpredictable rate before leveling off. What should a solutions architect do to ensure the system can automatically scale for the increased traffic? (Choose two.)

The problem describes two bottlenecks: overloaded EC2 instances and an RDS instance running out of storage. 1. Configure storage Auto Scaling on the RDS for Oracle instance: This directly addresses the RDS storage issue. RDS Storage Auto Scaling automatically scales storage capacity based on usage, preventing outages due to insufficient space. 2. Configure the Auto Scaling group to use the average CPU as the scaling metric: The EC2 instances are overloaded, indicating high CPU utilization. Using average CPU utilization as a scaling metric allows the Auto Scaling group to automatically add or remove instances in response to demand, ensuring the application remains responsive. Migrating to Amazon Aurora is a significant architectural change and not the most direct or immediate solution for the current scaling problem, especially given the Oracle