Restrict access to InternalSecurityGroup. #253
Closed
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.
As discussed on Slack (https://concourseci.slack.com/archives/general/p1452624733008350) we would like to tighten our security group rules for the internal security group. Further to the discussion, it appears we needed to add access from the WebSecurityGroup as well as those mentioned.
Allow only the following sources to connect to InternalSecurityGroup on tcp and udp: InternalSecurityGroup, WebSecurityGroup, BOSHSecurityGroup.
The current configuration (InternalSecurityGroup is open to all sources on every port) causes amazon trusted advisor to raise a red warning.
Signed-off-by: Simon Jones simon@cloudcredo.com