Why are my Amazon Aurora cluster endpoints in the Creating status?

Last updated: 2020-08-31

Short description

When you create an Aurora cluster using the Amazon RDS console, the cluster populates with an Aurora DB instance (or two instances if you choose Multi-AZ configuration). This DB instance is implicitly created for the RDS console. After you create the cluster successfully, and the Aurora DB instances are in Available status, the Aurora endpoints are also in the Available status.

If you run create-db-cluster using AWS Command Line Interface (AWS CLI) or use CreateDBCluster API calls to create your Aurora cluster, then you create an empty Aurora cluster without any DB instances. The statuses of your Aurora endpoints in the Amazon RDS console are in the Creating status, because the Aurora cluster does not have any DB instances.

To create DB instances for the cluster, use the create-db-instance or the CreateDBInstance API.

Resolution

Note: If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.

Invoke create-db-instance using the AWS CLI or use the CreateDBInstance API to populate the existing Aurora cluster with Aurora DB instances.

The following example command uses AWS CLI to create an Aurora DB instance for an existing Aurora cluster:

aws rds create-db-instance --db-instance-identifier sample-instance
     --db-cluster-identifier sample-cluster --engine aurora-mysql --db-instance-class db.r4.large --db-parameter-group aurora_pg --port 3306 --publicly-accessible

After you have created the Aurora DB instance, and your Aurora DB instance is in the Available status, the Aurora endpoints are also in the Available status.

Related information

Creating an Amazon Aurora DB cluster

Tools to build on AWS