- Newest
- Most votes
- Most comments
Based on the information provided, there are a few potential issues that could be causing your secondary cluster to remain stuck in the "Creating" state:
KMS Key Access Issue:
While you've updated the KMS permissions, Aurora Global Database has a specific limitation regarding encryption credentials. If Aurora loses access to the AWS KMS key for the DB cluster, the encrypted DB cluster can go into an inaccessible-encryption-credentials state. Since you mentioned the KMS permissions were initially missing, this could have caused the creation process to fail. Even though you've since corrected the permissions, the cluster creation may have already encountered a terminal state.
Engine Version Compatibility: Ensure that your primary DB cluster is also running Aurora PostgreSQL 17.4. It's recommended that secondary clusters use the same DB engine version as the primary cluster to avoid compatibility issues during the replication setup.
Primary Cluster Source: If your primary DB cluster was created as a replica of an Amazon RDS PostgreSQL instance (not an Aurora cluster), you cannot create secondary clusters from it. Attempts to do so will time out and the secondary cluster won't be created successfully.
Recommended Actions:
- Check the primary cluster's engine version matches the secondary (17.4)
- Verify the primary cluster wasn't originally created from an RDS PostgreSQL replica
- Consider deleting the stuck secondary cluster and recreating it now that KMS permissions are properly configured
- Monitor the cluster status and check CloudWatch logs for any specific error messages
If the issue persists after verifying these points, you may need to engage AWS Support directly for deeper investigation into the cluster creation logs.
Sources
Using Amazon Aurora Global Database - Amazon Aurora
Adding an AWS Region to an Amazon Aurora global database - Amazon Aurora
Relevant content
asked 3 years ago
