docs/route53_records_exclusive: ChangeResourceRecordSets AWS API limits#47497
Open
oycyc wants to merge 3 commits intohashicorp:mainfrom
Open
docs/route53_records_exclusive: ChangeResourceRecordSets AWS API limits#47497oycyc wants to merge 3 commits intohashicorp:mainfrom
oycyc wants to merge 3 commits intohashicorp:mainfrom
Conversation
…uest limits The aws_route53_records_exclusive resource sends all diffed changes in a single ChangeResourceRecordSets request with no chunking. Add a note to the resource documentation explaining the 1,000 ResourceRecord element per-request limit, the UPSERT double-count rule, and worked examples so users can anticipate apply-time failures on large hosted zones.
Contributor
Community GuidelinesThis 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
Pull Request Authors
|
github-actions
Bot
added
needs-triage
justinretzolk
requested changes
Apr 16, 2026
justinretzolk
added
the
waiting-response
Co-authored-by: Justin Retzolk <44710313+justinretzolk@users.noreply.github.com>
oycyc
commented
Apr 16, 2026
Contributor
Author
|
@justinretzolk updated PR accordingly, thanks for feedback |
github-actions
Bot
removed
the
waiting-response
ewbankkit
removed
the
needs-triage
Contributor
|
@oycyc Thanks for the contribution 👏. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The
aws_route53_records_exclusiveresource batches every diffed change (CREATE/DELETE/UPSERT) from anapplyinto a singleChangeResourceRecordSetsrequest. The provider does not split changes across multiple requests, so applies that exceed the AWS per-request limit fail atapplytime with no automatic retry or chunking.The AWS limit is 1,000
ResourceRecordelements per request, andUPSERTactions count each element twice — meaning modifications hit the cap at ~500 records. This was previously undocumented, so users managing larger hosted zones could hit unexpected failures on initial creates or bulk updates.This PR adds a callout to the resource documentation covering:
UPSERTdouble-count rule.UPSERTbatches).No code changes.
References
Output from Acceptance Testing
N/A — documentation only.