RDS global cluster major version upgrade when the global cluster is created from existing DB Cluster

[Rustege]

Description

When we create rds global cluster from an existing cluster (Reference), we couldn't perform RDS major version upgrade.

Reasons

• As mentioned in the document, we used source_db_cluster_identifier in aws_rds_global_cluster and couldn't pass engine or engine_version while doing a major version upgrade.

At present I couldn't find a way to perform major version upgrade when we create global cluster from an existing cluster.

Errors received:

  aws_rds_cluster.rds_cluster[0]: Modifying... [id=deve-inspec-rds0-module-aurora-postgresql]
       ╷
       │ Error: updating RDS Cluster (deve-imodule-aurora-postgresql): InvalidParameterCombination: Major Version Upgrade isn't supported in a single member of a global cluster. Use ModifyGlobalCluster to upgrade all the members.
       │    status code: 400, request id: xxxx
       │ 
       │   with aws_rds_cluster.rds_cluster_secondary[0],
       │   on aurora-secondary.tf line 49, in resource "aws_rds_cluster" "rds_cluster_secondary":
       │   49: resource "aws_rds_cluster" "rds_cluster_secondary" {
       │ 
       ╵
       ╷
       │ Error: updating RDS Cluster (deve-module-aurora-postgresql): InvalidParameterCombination: Major Version Upgrade isn't supported in a single member of a global cluster. Use ModifyGlobalCluster to upgrade all the members.
       │    status code: 400, request id: xxx
       │ 
       │   with aws_rds_cluster.rds_cluster[0],
       │   on aurora.tf line 39, in resource "aws_rds_cluster" "rds_cluster":
       │   39: resource "aws_rds_cluster" "rds_cluster" {

References

No response

Would you like to implement a fix?

None

[github-actions[bot]]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[CharlesDMoore]

Has there been any update with this? Only workaround we've been able to do is upgrading the global cluster manually and then matching TF code to the new values.