-
Notifications
You must be signed in to change notification settings - Fork 118
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.
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
Add the ability to allow access based on security group ID #29
Add the ability to allow access based on security group ID #29
Conversation
This should allow us to pass CIDR blocks to the Security Group, which lets us use this module for internal bastion hosts, or bastion hosts that shouldn't be open to the world.
README.md
Outdated
@@ -27,6 +27,7 @@ Only SSH access is allowed to the bastion host. | |||
* `eip` - EIP to put into EC2 tag (can be used with scripts like https://github.com/skymill/aws-ec2-assign-elastic-ip, default - empty value) | |||
* `key_name` - Launch configuration key name to be applied to created instance(s). | |||
* `allowed_cidr` - A list of CIDR Networks to allow ssh access to. Defaults to 0.0.0.0/0 | |||
* `allowed_security_groups` - A list of Security Group ID's to allow access to. Defaults to empty list |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It can be more descriptive if you say "A list of Security Group ID's to allow access to the bastion host (useful if bastion is deployed internally)".
done and done |
Cool. Update CHANGELOG as well, please. LGTM, you can now merge and tag it yourself :) |
Sweet, I am now drunk with power! 🔋 |
This is useful for internal bastion, so for example when you only want this host to be open to a particular SG rather then a CIDR range
Sorry about opening a second PR, I would have added to the previous one, but wasn't fast enough :p