You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've created a multi-region (3 regions) MySQL deployment with multi_az = true. So we have the primary instance and read-replicas in 2 other regions. It all applies successfully, no errors but on inspecting the infra in the AWS console I can see the primary instance is multi_az but the read-replicas (in different regions) are not.
If I do another terraform apply then terraform notices that the other regions are not multi_az and states that they will be set to true but on applying it remains stubbornly set to false.
Output of re-running terraform apply (not 2 other attributes also failed to take, backup retention and IAM access):
Terraform will perform the following actions:
~ module.rds-sydney.module.db.module.db_instance.aws_db_instance.this
backup_retention_period: "0" => "1"
iam_database_authentication_enabled: "false" => "true"
multi_az: "false" => "true"
Plan: 0 to add, 1 to change, 0 to destroy.
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value: yes
module.rds-sydney.module.db.module.db_instance.aws_db_instance.this: Modifying... (ID: test-multiregion-rds-sydney)
backup_retention_period: "0" => "1"
iam_database_authentication_enabled: "false" => "true"
multi_az: "false" => "true"
module.rds-sydney.db.db_instance.aws_db_instance.this: Still modifying... (ID: test-multiregion-rds-sydney, 10s elapsed)
module.rds-sydney.db.db_instance.aws_db_instance.this: Still modifying... (ID: test-multiregion-rds-sydney, 20s elapsed)
module.rds-sydney.db.db_instance.aws_db_instance.this: Still modifying... (ID: test-multiregion-rds-sydney, 30s elapsed)
module.rds-sydney.module.db.module.db_instance.aws_db_instance.this: Modifications complete after 37s (ID: test-multiregion-rds-sydney)
Apply complete! Resources: 0 added, 1 changed, 0 destroyed.
The text was updated successfully, but these errors were encountered:
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. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
I've created a multi-region (3 regions) MySQL deployment with multi_az = true. So we have the primary instance and read-replicas in 2 other regions. It all applies successfully, no errors but on inspecting the infra in the AWS console I can see the primary instance is multi_az but the read-replicas (in different regions) are not.
If I do another terraform apply then terraform notices that the other regions are not multi_az and states that they will be set to true but on applying it remains stubbornly set to false.
I am able to turn it on in the AWS console and I notice this seems to be a recent feature: https://aws.amazon.com/about-aws/whats-new/2018/01/amazon-rds-read-replicas-now-support-multi-az-deployments/ - perhaps this is why it is not working?
Output of re-running terraform apply (not 2 other attributes also failed to take, backup retention and IAM access):
The text was updated successfully, but these errors were encountered: