An application on AWS uses an Amazon Aurora MySQL DB instance that is experiencing too many open connections. Most application operations are inserts. Database credentials are currently stored in a plaintext configuration file. The solutions architect must design a solution that handles the current connection load, secures credentials, and supports automatic credential rotation on a regular schedule. Which solution satisfies these requirements?

The correct solution is to deploy Amazon RDS Proxy in front of the Aurora DB instance and store the database credentials as a secret in AWS Secrets Manager. RDS Proxy efficiently manages database connections, reducing the number of open connections to the Aurora instance, which directly addresses the "too many open connections" problem. It also enables automatic credential rotation when integrated with AWS Secrets Manager. Storing credentials in Secrets Manager provides a secure way to manage and rotate them, fulfilling the security and rotation requirements. Storing credentials in AWS Systems Manager Parameter Store does not support automatic credential rotation, making it unsuitable for the requirement. Creating an Aurora Replica helps offload read traffic but does not solve the "too many open connections" issue for write operations, which are the primary concern given that most operations are inserts.