Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix bastion security groups #611

Open
tayzlor opened this issue Jan 8, 2016 · 0 comments
Open

Fix bastion security groups #611

tayzlor opened this issue Jan 8, 2016 · 0 comments
Labels
bug coreos provider/aws

Comments

@tayzlor
Copy link
Member

tayzlor commented Jan 8, 2016

We provision bastion with

security_groups   = ["${module.sg-default.security_group_id}", "${aws_security_group.bastion.id}"]

This actual means bastion is connectable on any port (default security group is open). It shouldn't be the case

This isn't actual a problem specific to coreOS - it exists in master as well AFAIK
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug coreos provider/aws
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tayzlor