[Bug]: aws_rds_orderable_db_instance, MaxRecords is too high

[faymard]

Terraform Core Version

1.6.5

AWS Provider Version

5.47.0

Affected Resource(s)

aws_rds_orderable_db_instance

Expected Behavior

This datasource allows us to get information on DB instance types.

Actual Behavior

We encounter a 400 status code while querying this data source. The message is shown below.

Relevant Error/Panic Output Snippet

╷
│ Error: reading RDS Orderable DB Instance Options: InvalidParameterValue: Invalid value 3412 for MaxRecords. Must be between 20 and 1000
│ 	status code: 400, request id: c414083f-ffbc-4a8e-9ae0-ec81a14afe93
│ 
│   with module.amiante_exposition-db.data.aws_rds_orderable_db_instance.rds_instance_info,
│   on terraform_modules/aws-rds/05_datasources.tf line 8, in data "aws_rds_orderable_db_instance" "rds_instance_info":
│    8: data "aws_rds_orderable_db_instance" "rds_instance_info" {
│ 
╵

Terraform Configuration Files

data "aws_rds_orderable_db_instance" "rds_instance_info" {
  engine         = var.engine
  engine_version = var.engine_version
  instance_class = var.instance_type
  storage_type   = var.storage_type
}

Steps to Reproduce

• Run terraform plan
• Error is raised right after

Debug Output

No response

Panic Output

No response

Important Factoids

Going to versions 5.36.0 and below "solves" this error.

References

The value given in the error message seems to be hardcoded here and packaged from version 5.37.0.

terraform-provider-aws/internal/service/rds/orderable_instance_data_source.go

Line 217 in 3c35893

MaxRecords: aws.Int64(3412),

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.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions]

This functionality has been released in v5.49.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. Thank you!

[github-actions]

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.