Connect to your Amazon Aurora MySQL DB cluster

Connect to your DB cluster

To authenticate to your Aurora MySQL-Compatible DB cluster, you can use either MySQL username and password authentication or AWS Identity and Access Management (IAM) database authentication.

• For more information on using MySQL user name and password authentication, see Access control and account management in the MySQL documentation.
• For more information on using IAM database authentication, see IAM database authentication.

For information on connecting to your cluster and connection utilities, see Connecting to an Aurora MySQL DB cluster. For detailed guidance on connecting to an Aurora MySQL DB cluster, see the Aurora connection management handbook. To download standards-based drivers for JDBC, ODBC, and .NET, see MySQL Connectors in the MySQL documentation.

To establish connections to the MySQL Server, for clients such as mysql or mysqldump, use the command-line options listed in the MySQL documentation.

If you're managing connections with Amazon Relational Database Service (Amazon RDS) Proxy, see How do I connect to my Amazon RDS MySQL DB instance or Aurora MySQL DB cluster using Amazon RDS Proxy?

Connection pooling is a way to create and manage a pool of connections that are ready for use by any thread that needs them. Connection pooling can greatly increase the performance of your Java application, while reducing overall resource usage. For more information, see Connection pooling with Connector/J in the MySQL documentation.

Work with a DB cluster in an Amazon VPC

Your default Amazon Virtual Private Cloud (Amazon VPC) has three subnets that you can use to isolate resources inside the Amazon VPC. The default Amazon VPC has an internet gateway that you can use to provide access to resources inside the Amazon VPC from outside. For more information, see Working with a DB cluster in a VPC. For a list of scenarios about using Amazon Aurora DB clusters in an Amazon VPC, see Scenarios for accessing a DB cluster in a VPC.

The Amazon VPC security groups control the access that traffic has in and out of a DB cluster. By default, network access is turned off for a DB cluster. You can specify rules in a security group that allow access from an IP address range, port, or security group. After you configure the ingress rules, the same rules apply to all DB clusters that are associated with that security group. You can specify up to 20 rules in a security group. For more information, see Controlling access with security groups.

This example scenario is a common security group setup that you can use to share data with an application server that runs in an Amazon Elastic Compute Cloud (Amazon EC2) instance in the same VPC that's accessed by a client application outside the VPC:

Diagnose communication errors and connection failures

To troubleshoot connection issues with Amazon Aurora, see How do I troubleshoot problems connecting to Amazon Aurora?

To troubleshoot a connection problem with your Aurora MySQL DB cluster, review Communication errors and aborted connections in the MySQL documentation.

To diagnose the SERVER GONE error code, see MySQL server has gone away in the MySQL documentation.

To troubleshoot a lost connection to the server, see Lost connection to MySQL server in the MySQL documentation.

To resolve the "Too Many Connections" error, see Why am I getting a "Too Many Connections" error when connecting to my Amazon Aurora MySQL instance?

Related resources

AWS JDBC Driver for MySQL