[wip] Restrict egress on rift_compute security-group to known destinations + allow extension. #157
Conversation
This file contains 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
…on-control-plane (step 1: leave 0.0.0.0/0 rule in)
…ictions behind variable.
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.
Adding
apply_egress_restrictionsinput variable torift_computemodule. If set to true,rift_computesecurity-group will have egress restricted to the known destinations -- chronosphere, fluentbit-packages, and tecton control plane.If PrivateLink is enabled, rift_compute SG will have egress rule to allow access to the local vpc-endpoint that gets created in this module.