Which solution will meet these requirements MOST cost-effectively?
Modify the instance class to db.r3.xlarge. Apply the changes immediately.
Edit the default parameter group for the MySQL engine that the database uses. Change the max_connections value to 2,000. Reboot the DB instance to apply the new value.
Create a new parameter group for the MySQL engine that the database uses. Set the max_connections value to 2,000. Assign the parameter group to the DB instance. Apply the changes immediately.
Modify the instance class to db.t3.large. Apply the changes immediately.
Explanations:
The db.r3 instance class is not supported in Amazon Aurora Serverless, which auto-scales resources dynamically. Moving to db.r3.xlarge will not resolve issues with connection limits or cost-effectiveness, as db.r3 instances are older and intended for provisioned setups.
Editing the default parameter group to increase max_connections to 2,000 is not ideal. Adjusting this parameter alone does not guarantee the Aurora Serverless cluster will have enough resources to handle 2,000 connections, and modifying the default parameter group can impact other databases using it.
Creating a new parameter group and setting max_connections to 2,000 is the best solution. It allows Aurora Serverless to scale to meet the connection requirements without modifying default settings. Applying a custom parameter group ensures dedicated configurations for this database alone, meeting the 2,000 connections requirement efficiently.
Modifying the instance class to db.t3.large does not resolve the issue, as the db.t3 instance family is not optimized for higher connection limits. The issue is not about instance size but configuring Aurora Serverless to handle more connections.
If I’m not mistaken, the answer is:
Create a new parameter group for the MySQL engine that the database uses. Set the max_connections value to 2,000. Assign the parameter group to the DB instance. Apply the changes immediately.