data-source/aws_docdb_orderable_db_instance: New data source

[YakDriver]

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 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
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Relates #14882

Description

Knowing which combinations of DB instance class, engine, engine version, and license model are available is non-trivial especially in GovCloud and other specialty partitions. For example, attempting to use a t3.small on GovCloud, a valid option for us-west-2 in the standard partition, gives this error:

Error creating DB Instance: InvalidParameterCombination: RDS does not support creating a DB instance with the
following combination: DBInstanceClass=db.t3.small, Engine=mysql, EngineVersion=5.6.41, LicenseModel=
general-public-license. For supported combinations of instance class and database engine version, see the
documentation.

I envision something similar to aws_ec2_instance_type_offering.

New or Affected Resource(s)

• aws_docdb_orderable_db_instance

Potential Terraform Configuration

data "aws_docdb_orderable_db_instance" "test" {
  engine         = "docdb"
  engine_version = "3.6.0"
  license_model  = "na"

  preferred_db_instance_classes = ["db.r6.xlarge", "db.m4.large", "db.t3.small"]
}

resource "aws_docdb_cluster_instance" "test" {
  cluster_identifier = aws_docdb_cluster.test.id
  instance_class     = data.aws_docdb_orderable_db_instance.test.db_instance_class
}
...

References

• resource/db_instance
• data-source/db_instance
• data-source/ec2_instance_type_offering

[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!