-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot create global RDS Aurora cluster #10188
Comments
Hi there, Could somebody from AWS provider contributors please take a look? Since it doesn't work via TF we had to implement the same functionality via AWS CLI, but hope to get it working via Terraform some day. Appreciate your help. |
Hi there, this is still an issue - I have the same issue with creating a rds global cluster. The rds global cluster gets created but when I try to create an rds cluster as the primary cluster for the global cluster, it fails with error - * aws_rds_cluster.primary: error creating RDS cluster: InvalidParameterValue: The engine mode global you requested is currently unavailable. I am using Terraform version 0.11.11 |
Using provider v2.57.0 and terraform 0.12.24, this issue is still happening. If I provide a username for secondary cluster, terraform fails with
If I don't provide one, it fails with
|
Just for the sake of experimentation, I switched to mysql engine from postgres and that went through. Another colleague of mine also was able to successfully stand up a mysql cluster. So it seems the problem is with postgres sql engine This is what I had before
and now:
|
I think I figured out the magic combo to make it work with Postgres:
Specifying And then you don't specify it for any of the cluster but make sure you provide username/password for primary (but not
So in summary:
|
Note that although it now succeeds, it doesn't create the initial database as specified by
|
I managed to create the initial database, it required setting up the database name both at the global resources as well as the primary cluster resource level. So using the same setup as mentioned in my earlier comment, just add
It seems redundant to set it up for both global and primary but that's what did the trick. |
This thing drives me crazy... but after many tests i've finally something up and running From my testings and values to be set :
So to resume here is (for me) the terraform missing points
And to finalize be able to use storage_encrypted with true value. I now to test if everythings works as intended |
I tried creating Global Cluster for PostgreSQL and got the below error using terraform . Works absolutely fine for Aurora MySQL. λ terraform apply --var-file=env/dev.tfvars Error: expected engine to be one of [aurora aurora-mysql], got aurora-postgresql on main.tf line 32, in resource "aws_rds_global_cluster" "rds_global_cluster": terraform { required_providers { |
I am using v3.37.0 of the AWS provider and this issue persists. If it was ever fixed it clearly has regressed. |
This has been released in version 3.43.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
n/a. (The error is a standard API error)
Panic Output
n/a
Expected Behavior
Provision a global Aurora RDS cluster
Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
If the Username and Password is provided for the primary RDS cluster, the primary cluster can be created, but the secondary fails.
If both primary and secondary clusters are provided with a Username and Password, the error is:
References
This behavior is exactly the same as reported in
It was supposed to be fixed in AWS provider version 1.60, but even after installing that old version I got the same errors/behavior.
Note that Username and Password should be optional when
global_cluster_identifier
is provided inaws_rds_cluster
as stated in https://www.terraform.io/docs/providers/aws/r/rds_cluster.html#master_passwordThe text was updated successfully, but these errors were encountered: