bug: APIGateway (REST/V1) aws_api_gateway_api_key.value minimum length is incorrect

[tamiros]

This PR fixes the bug where Terraform had a minimum length for the argument value of 30 characters instead of 20 in the resource aws_api_gateway_api_key.

Unfortunately, AWS didn't specify this constraint in the documentation (API Reference, CLI, CloudFormation) but only in that particular page.

It is in fact limited to a minimum of 20 characters and not 30 as tested via the CLI and Web Console.

An error occurred (BadRequestException) when calling the CreateApiKey operation: API Key value should be at least 20 characters
An error occurred (BadRequestException) when calling the CreateApiKey operation: API Key value exceeds maximum size of 128 characters

Relations

Closes #30872

References

https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-usage-plans.html#apigateway-usage-plans-best-practices

Output from Acceptance Testing

$ make testacc TESTS='TestAccAPIGatewayAPIKey_value' PKG=apigateway
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/apigateway/... -v -count 1 -parallel 20 -run='TestAccAPIGatewayAPIKey_value'  -timeout 180m
=== RUN   TestAccAPIGatewayAPIKey_value
=== PAUSE TestAccAPIGatewayAPIKey_value
=== CONT  TestAccAPIGatewayAPIKey_value
--- PASS: TestAccAPIGatewayAPIKey_value (17.78s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/apigateway 17.850s

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull 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.

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[ewbankkit]

LGTM 🚀.

[ewbankkit]

@tamiros Thanks for the contribution 🎉 👏.

[github-actions]

This functionality has been released in v4.65.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 pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.