In an Aurora Global Database setup, you need to specify the GlobalClusterIdentifier property when you create a secondary cluster in a secondary region.
However, the DBCluster CFN does not appear to know how to retrieve the current value of GlobalClusterIdentifier and thinks it is null, which causes Drift Detection on the secondary cluster to report that it is in drift.
The DBCluster CFN resource could either lookup the current runtime value of GlobalClusterIdentifier by scanning through the output of the rds describe-global-clusters output to see if the cluster is listed, OR you could ignore the GlobalClusterIdentifier property when calculating drift detection.
Expected Behavior
As long as a DBCluster is still part of the same GlobalCluster setup, we do not expect a stack that specified GlobalClusterIdentifier for DBCluster should ever be marked as out of sync on an unchanged GlobalClusterIdentifier property.
Observed Behavior
The GlobalClusterIdentifier is marked as REMOVED during drift-detection.
Create a Global Cluster setup using CFN with a primary in region1 and a secondary cluster in region2.
After the secondary cluster is created, run a drift detection on the stack that created the secondary cluster.
You will see that the GlobalClusterIdentifier property of the secondary cluster is marked as in DRIFT.
Name of the resource
AWS::RDS::DBCluster
Resource Name
No response
Issue Description
In an Aurora Global Database setup, you need to specify the GlobalClusterIdentifier property when you create a secondary cluster in a secondary region.
However, the DBCluster CFN does not appear to know how to retrieve the current value of GlobalClusterIdentifier and thinks it is null, which causes Drift Detection on the secondary cluster to report that it is in drift.
The DBCluster CFN resource could either lookup the current runtime value of GlobalClusterIdentifier by scanning through the output of the rds describe-global-clusters output to see if the cluster is listed, OR you could ignore the GlobalClusterIdentifier property when calculating drift detection.
Expected Behavior
As long as a DBCluster is still part of the same GlobalCluster setup, we do not expect a stack that specified GlobalClusterIdentifier for DBCluster should ever be marked as out of sync on an unchanged GlobalClusterIdentifier property.
Observed Behavior
The GlobalClusterIdentifier is marked as REMOVED during drift-detection.
Test Cases
Create a Global Cluster setup using CFN with a primary in region1 and a secondary cluster in region2. After the secondary cluster is created, run a drift detection on the stack that created the secondary cluster. You will see that the GlobalClusterIdentifier property of the secondary cluster is marked as in DRIFT.
Other Details
No response