When I use AWS Backup to restore an Amazon Aurora cluster endpoint, the cluster gets stuck in the Creating status.
Resolution
Note: If you receive errors when you run AWS Command Line Interface (AWS CLI) commands, then see Troubleshooting errors for the AWS CLI. Also, make sure that you're using the most recent AWS CLI version.
After you use AWS Backup to restore an Aurora cluster, the restore job shows the Completed status. However, the Amazon Relational Database Service (Amazon RDS) console shows the Creating status until you manually attach the Amazon RDS instances to the restored cluster. Because you store the data in the cluster, the backup restoration restores only the cluster, not the instances.
Note: If you use the AWS Management Console to restore a DB cluster from a snapshot, then you also create the primary DB instance.
Aurora creates the endpoints only after you manually create the RDS instances in the restored cluster.
To manually attach the new instances to the Aurora cluster, run the following create-db-instance AWS CLI command:
aws rds create-db-instance --db-instance-identifier INSTANCE-NAME --db-cluster-identifier CLUSTER-NAME --engine ENGINE-NAME --db-instance-class SIZE-TYPE --region REGION-NAME
Note: In the preceding command, replace INSTANCE-NAME with the name of your instance and CLUSTER-NAME with the name of your restored cluster. Also, replace ENGINE-NAME with the cluster's engine name, SIZE-TYPE with your cluster's instance class, and REGION-NAME with the AWS Region that your cluster is in.
After you create the instance, the endpoints in the cluster are in the Available status.