Error in aws_rds_cluster engine_mode not supported in Singapore

[facundo-guerrero-olx]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Terraform v0.10.8

Affected Resource(s)

• aws_rds_cluster

Debug Output

Panic Output

Error: Error applying plan:

1 error(s) occurred:

* module.rds_aurora_mydb.aws_rds_cluster.default: 1 error(s) occurred:

* aws_rds_cluster.default: error creating RDS cluster: InvalidParameterValue: The engine mode provisioned you requested is currently unavailable.
	status code: 400, request id: db186c68-2908-4f7c-b639-9004871288be

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Expected Behavior

Actual Behavior

Singapore does not support engine mode.

Steps to Reproduce

Create an aurora cluster in Singapore using the version of the provider > 1.32

1. terraform apply

References

#5503

[bflad]

Hi @facundo-guerrero-olx 👋

I'm not able to reproduce the issue with this configuration:

provider "aws" {
  region  = "ap-southeast-1"
  version = "1.32.0"
}

resource "aws_rds_cluster" "test" {
  cluster_identifier  = "issue-5593-testing"
  engine              = "aurora"
  master_username     = "username"
  master_password     = "password"
  skip_final_snapshot = true
}

Nor with engine = "aurora-mysql" or engine = "aurora-postgresql".

Can you please provide additional details about your configuration that is failing? Thanks!

[facundo-guerrero-olx]

@bflad you need to use engine_version = mysql-5.7

[bflad]

@facundo-guerrero-olx if you're looking to run Aurora 2.X (MySQL 5.7) with the aws_rds_cluster resource while also specifying the engine_version (optional), you need to set it to 5.7.12. This is fairly buried in the RDS documentation:

The engine version for Aurora MySQL 2.x is 5.7.12; the engine version for Aurora MySQL 1.x continues to be 5.6.10ann.

For example, this configuration applies successfully:

provider "aws" {
  region  = "ap-southeast-1"
  version = "1.32.0"
}

resource "aws_rds_cluster" "test" {
  cluster_identifier  = "issue-5593-testing"
  engine              = "aurora-mysql"
  engine_version      = "5.7.12"
  master_username     = "username"
  master_password     = "password"
  skip_final_snapshot = true
}

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

When providing an invalid engine_version (like engine_version = "mysql-5.7"), it seems the RDS API returns back the unhelpful error message:

aws_rds_cluster.test: Creating...
  apply_immediately:               "" => "<computed>"
  arn:                             "" => "<computed>"
  availability_zones.#:            "" => "<computed>"
  backup_retention_period:         "" => "1"
  cluster_identifier:              "" => "issue-5593-testing"
  cluster_identifier_prefix:       "" => "<computed>"
  cluster_members.#:               "" => "<computed>"
  cluster_resource_id:             "" => "<computed>"
  database_name:                   "" => "<computed>"
  db_cluster_parameter_group_name: "" => "<computed>"
  db_subnet_group_name:            "" => "<computed>"
  endpoint:                        "" => "<computed>"
  engine:                          "" => "aurora-mysql"
  engine_mode:                     "" => "provisioned"
  engine_version:                  "" => "mysql-5.7"
  hosted_zone_id:                  "" => "<computed>"
  kms_key_id:                      "" => "<computed>"
  master_password:                 "<sensitive>" => "<sensitive>"
  master_username:                 "" => "username"
  port:                            "" => "<computed>"
  preferred_backup_window:         "" => "<computed>"
  preferred_maintenance_window:    "" => "<computed>"
  reader_endpoint:                 "" => "<computed>"
  skip_final_snapshot:             "" => "true"
  vpc_security_group_ids.#:        "" => "<computed>"

Error: Error applying plan:

1 error(s) occurred:

* aws_rds_cluster.test: 1 error(s) occurred:

* aws_rds_cluster.test: error creating RDS cluster: InvalidParameterValue: The engine mode provisioned you requested is currently unavailable.
	status code: 400, request id: 06c9e9c5-ad07-4060-919d-5ad4d41a97bb

Since that message is generated by the RDS API, a feature request would have to be submitted through AWS Support to get that potentially updated.

Within the Terraform resource itself, we do not currently provide any guardrails against misconfiguring the engine_version argument since it could present a maintenance burden.

[bflad]

Given there should be a solution provided above for correctly configuring Terraform in this situation and the incorrect error messaging needs to be fixed by the RDS API, I am not sure there is anything to do with this issue so I'm going to close it for now. Please let me know if you think that is incorrect for some reason.

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!