A company runs applications that connect to an Amazon RDS database. The applications scale on weekends and during peak seasons. The company wants to scale database connections with the LEAST operational overhead. Which solution meets this requirement?

Amazon RDS Proxy is the most suitable solution because it provides fully managed, highly available database connection pooling, which automatically handles the fluctuating connection demands of scaling applications with minimal operational overhead. Applications connect to the RDS Proxy endpoint, and the proxy manages the connections to the RDS database, efficiently reusing them and reducing the burden on the database. Using Amazon DynamoDB is incorrect because it's a NoSQL database, fundamentally different from RDS (relational), and would require significant application re-architecture, not just connection scaling. A custom proxy on EC2 would introduce significant operational overhead for management, patching, and scaling.