Why is my Aurora cluster endpoint stuck in the "Creating" state after the AWS Backup restore job is completed?

Resolution

When you use AWS Backup to restore an Aurora cluster, the restore job is marked as Completed. However, until you manually attach the Amazon Relational Database Service (Amazon RDS) instances to the restored cluster, the Amazon RDS console shows the Creating status. The backup restoration restores only the cluster and not the instances because the data is stored in the cluster.

Endpoints aren't created until you manually create the RDS instances in the restored cluster.

To resolve this issue, manually attach the new instances to the Aurora cluster with the following command:

Note: 

• Replace clustername with the newly restored cluster name.
• Replace enginename with the cluster's engine name from the configuration page of your cluster. For example, aurora-mysql.
• Replace sizetype with the instance class of your cluster. For example, db.r6g.2xlarge.
• Replace regionname with the AWS Region where your cluster is.

aws rds create-db-instance --db-instance-identifier <instancename> --db-cluster-identifier <clustername> --engine <enginename> --db-instance-class <sizetype> --region <regionname>

Note: When running AWS Command Line Interface (AWS CLI) commands, make sure that you're using the most recent AWS CLI version.

The preceding command creates an instance and attaches it to the restored cluster. After the instance is created, the endpoints in the cluster are in the Available status.