Restrict MQ security group ingress to VPC CIDR in integration test#3884
Merged
Restrict MQ security group ingress to VPC CIDR in integration test#3884
Conversation
bnusunny
approved these changes
Feb 17, 2026
vicheey
approved these changes
Feb 17, 2026
roger-zhangg
approved these changes
Feb 17, 2026
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
4 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.
The MQSecurityGroup in function_with_mq_using_autogen_role.yaml and function_with_mq.yaml was allowing ingress from 0.0.0.0/0, triggering Policy Engine violations in test account.
Since this is an integration test that only validates CloudFormation resource creation (no actual MQ message sending), restrict ingress to the companion stack VPC CIDR (10.0.0.0/16) instead of the public internet.
This prevents security groups from being flagged in Policy Engine risk assessment.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.