Which solution will meet these requirements?

Explanations:

Deploying an Amazon RDS Proxy in front of the DB instance helps to manage database connections efficiently and supports connection pooling, which can alleviate the overload on the database. Storing the connection credentials in AWS Secrets Manager ensures that they are secured and can be rotated automatically, meeting the security and credential rotation requirements.

While deploying an Amazon RDS Proxy is a good approach for managing database connections, storing credentials in AWS Systems Manager Parameter Store does not provide the same level of security and automated rotation features as AWS Secrets Manager. This option fails to fully meet the requirement for secure and easily rotatable credentials.

Creating an Aurora Replica can help with read scaling but does not address the connection overload issue directly. Additionally, while storing credentials in AWS Secrets Manager is a good practice, this option does not include a solution for connection management like the RDS Proxy, making it inadequate for the specified requirements.

Similar to option C, creating an Aurora Replica does not help with the connection overload problem, and while using AWS Systems Manager Parameter Store for credentials is acceptable, it does not provide the robust security and automatic rotation capabilities of AWS Secrets Manager. This option does not fulfill the requirements effectively.