How do I troubleshoot problems connecting to an Amazon Relational Database Service (Amazon RDS) cluster or instance that is running Amazon Aurora?

Here are some of the most common causes for issues connecting to an Amazon Aurora DB cluster or instance:

  • The Aurora DB cluster or instance is still being created and is not yet in the available state.
  • The DB instance security group, ACLs, or a local firewall are blocking the connection from the source instance or its IP addresses.
  • The route table that is associated with your VPC's subnets is not allowing or routing traffic from your local machine or DB instance.
  • The DB instance is not publicly accessible when connecting from a local machine through the internet.
  • DNS name resolution is failing, potentially because the client isn't connecting to the correct Aurora endpoint.

For help resolving common connection problems on Amazon RDS, including Aurora instances, see How do I resolve problems connecting to my Amazon RDS database instance?

For Aurora DB clusters, be sure that your client is connecting to the correct endpoint. Because Amazon Aurora is a managed service, you must connect to Aurora DNS endpoints using MySQL client tools.

Make sure that you connect to the correct Aurora endpoint. To verify the cluster, reader, and custom endpoints that your client is currently connecting to, follow these steps:

  1. Open the Amazon RDS console.
  2. Choose Clusters from the navigation pane.
  3. Choose your DB cluster in the Cluster, and then review the cluster details in the Cluster view.

You can perform an nslookup or dig against the Aurora endpoint to make sure that the DNS endpoint resolves correctly. For example, if you run nslookup using the cluster endpoint, and the endpoint resolves to the IP address of the current primary instance, then you receive a response similar to the following:

Non-authoritative answer:
Name:     {endpoint of your DB instance}
Address:  {IP address of your DB instance}

Note: An output similar to this does not guarantee that the traffic from your connection source will route properly to the endpoint.

Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center

Published: 2017-01-10

Updated: 2019-01-17