Allow traffic from self in Bastion SG #23
Merged
Conversation
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
paulo-cisco
approved these changes
Jun 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
#22 added restrictions on the Bastion SG.
Some example configurations put the primary ENA of each EC2 instance in the Bastion SG. This used to be fine for access - because the Bastion SG was open to everyone, so you could SSH to the Bastion, and then to the EC2 instance.
This is now not possible if you restrict traffic to the Bastion to certain CIDRs. You can SSH to the Bastion, but you cannot then jump to the EC2 instance, because traffic no longer originates at the allowed CIDR.
Add an SGR to the Bastion SG to allow all traffic from itself.