[Bug]: expected serverlessv2_scaling_configuration.0.max_capacity to be in the range (1.000000 - 256.000000), got 0.500000

[Klohto]

Terraform Core Version

1.10.5

AWS Provider Version

5.85.0

Affected Resource(s)

Using scaling configuration for Aurora v2 PSQL:

  serverlessv2_scaling_configuration {
    max_capacity             = 0.5
    min_capacity             = 0
    seconds_until_auto_pause = 300
  }

Expected Behavior

Allow setting the Aurora V2 instance to 0.5 as documented on AWS. I have also tried setting the value to be the same as min_capacity (both set to 0.5) as allowed by AWS and I get the same result

Actual Behavior

Doesn't allow lower value than 1.

Relevant Error/Panic Output Snippet

Error: expected serverlessv2_scaling_configuration.0.max_capacity to be in the range (1.000000 - 256.000000), got 0.500000

Terraform Configuration Files

Pasted config including references.

# Aurora V2 scaling to 0
resource "aws_rds_cluster" "aurora_psql" {
  cluster_identifier = "aurora-psql-testing"
  engine             = "aurora-postgresql"
  engine_mode        = "provisioned"
  engine_version     = "16.6"
  database_name      = "sandbox"
  master_username    = "postgresql"
  master_password    = "postgresql"
  storage_encrypted  = true
  db_subnet_group_name = aws_db_subnet_group.aurora_psql.id
  vpc_security_group_ids = [aws_security_group.aurora_psql.id]
  availability_zones = ["eu-west-1a", "eu-west-1b", "eu-west-1c"]

  serverlessv2_scaling_configuration {
    max_capacity             = 0.5
    min_capacity             = 0
    seconds_until_auto_pause = 300
  }
}

Steps to Reproduce

Use the config above

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[github-actions]

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.