You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
⚠️ Our automation has detected the following potential issues with your pull request
❌ Changelog Entry Required (Click to expand)
The proposed change requires a changelog entry. Please see the Changelog Process section of the contributing guide for information on the changelog generation process.
Tip: This check is not triggered for draft pull requests, since the pull request number is not known until the pull request is opened and is required to create a changelog entry. Opening a pull request first as a draft, adding the requisite changelog entry file, and then marking the pull request as ready for review will prevent future warnings.
djdabs
changed the title
IVS Chat: Increase maximum message rate validation to 100
b-aws_ivschat_room: Increase maximum message rate validation to 100
Oct 7, 2025
needs-triageWaiting for first response or review from a maintainer.service/ivschatIssues and PRs that pertain to the ivschat service.size/XSManaged by automation to categorize the size of a PR.
1 participant
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.
github-actions
bot
added
needs-triage
djdabs
changed the title
Rollback Plan
Set back to 10
Changes to Security Controls
None
Description
Bumping up validation for ivs chat room from 10 messages to 100.
The AWS API supports up to 100: https://docs.aws.amazon.com/ivs/latest/ChatAPIReference/API_CreateRoom.html#API_CreateRoom_RequestSyntax