New data source: aws_bedrockagentcore_gateway_rate_limit

[tobydoescode]

Rollback Plan

If a change needs to be reverted, we will publish an updated version of the library.

Changes to Security Controls

No changes to security controls. This adds a read-only data source.

Description

Important

This PR depends on #49429 and should be reviewed after it merges.

The resource and data source are deliberately split across two pull requests, following
docs/add-a-new-datasource.md:

Each data source should be submitted for review in isolation. Pull requests containing multiple data sources and/or resources are harder to review and the maintainers will normally ask for them to be broken apart.

#49429 adds the aws_bedrockagentcore_gateway_rate_limit resource; this PR adds the matching
data source.

Why the diff below is larger than this change. The data source branch is stacked on the
resource branch, and a cross-repo pull request cannot be based on a branch that exists only in the
fork — so GitHub shows both sets of commits here. Only the six files listed below belong to this
PR.

The split cannot be avoided by reordering. The data source genuinely depends on the resource:
its Read calls findGatewayRateLimitByTwoPartKey, defined in gateway_rate_limit.go, and its
_basic acceptance test creates a rate limit in order to read one back. I verified this by
rebasing onto main in a scratch worktree — the rebase applies with no conflicts, then fails to
build with undefined: findGatewayRateLimitByTwoPartKey. Decoupling would mean duplicating the
finder or bypassing it, both of which make the merged result worse.

Once #49429 merges I will rebase this branch onto main, and the diff will reduce to the six
files below. Happy to close and reopen instead if that is preferred.

Adds aws_bedrockagentcore_gateway_rate_limit, looking up a single rate limit on a Bedrock AgentCore Gateway by its identifier. This is the first data source in the bedrockagentcore service.

Files belonging to this change:

• internal/service/bedrockagentcore/gateway_rate_limit_data_source.go
• internal/service/bedrockagentcore/gateway_rate_limit_data_source_test.go
• internal/service/bedrockagentcore/testdata/GatewayRateLimitDataSource/{basic,not_found}/main.tf
• website/docs/d/bedrockagentcore_gateway_rate_limit.html.markdown
• .changelog/49440.txt

Two deliberate divergences from the resource, both noted in the data source documentation so they do not read as oversights:

• entries is a computed list attribute rather than a nested block. docs/add-a-new-datasource.md requires framework.DataSourceComputedListOfObjectAttribute for objects with only computed attributes, since fully computed blocks are not supported by Terraform protocol V6.
• status, created_at and updated_at are exported here but omitted on the resource, where a transient status would be state noise — the resource's waiters exist so practitioners never need to inspect it. aws_bedrock_inference_profile exposes all three on its data source.

Lookup is by rate_limit_id only, mirroring GetGatewayRateLimit. A dimension_keys lookup is also possible in principle, since that tuple is unique per gateway, but it would need a second code path over paginated ListGatewayRateLimits with order-sensitive client-side matching. It can be added later without breaking anyone.

Relations

Relates #49344
Depends on #49429

References

• GetGatewayRateLimit API reference
• Add rate limits to a gateway

Output from Acceptance Testing

% make testacc PKG=bedrockagentcore TESTS=TestAccBedrockAgentCoreGatewayRateLimitDataSource_

--- PASS: TestAccBedrockAgentCoreGatewayRateLimitDataSource_notFound (19.30s)
--- PASS: TestAccBedrockAgentCoreGatewayRateLimitDataSource_basic (30.62s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/bedrockagentcore   39.460s

The resource's nine acceptance tests also still pass on top of this branch:

% make testacc PKG=bedrockagentcore TESTS=TestAccBedrockAgentCoreGatewayRateLimit

--- PASS: TestAccBedrockAgentCoreGatewayRateLimit_duplicateDimensionKeys (28.81s)
--- PASS: TestAccBedrockAgentCoreGatewayRateLimit_multipleLimits (43.77s)
--- PASS: TestAccBedrockAgentCoreGatewayRateLimitDataSource_basic (44.88s)
--- PASS: TestAccBedrockAgentCoreGatewayRateLimit_disappears (45.50s)
--- PASS: TestAccBedrockAgentCoreGatewayRateLimit_basic (52.20s)
--- PASS: TestAccBedrockAgentCoreGatewayRateLimit_wildcards (56.28s)
--- PASS: TestAccBedrockAgentCoreGatewayRateLimit_Identity_regionOverride (64.37s)
--- PASS: TestAccBedrockAgentCoreGatewayRateLimit_forceNew (67.96s)
--- PASS: TestAccBedrockAgentCoreGatewayRateLimit_Identity_basic (68.69s)
--- PASS: TestAccBedrockAgentCoreGatewayRateLimit_update (86.28s)

Run in us-west-2 with Terraform v1.15.8.

[github-actions]

Community Guidelines

This comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Pull Request by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Pull Request and do not help prioritize the request.

Pull Request Authors

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.