You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 25, 2023. It is now read-only.
Currently the vault-cluster module requires at least 1 CIDR block to be passed in via the allowed_ssh_cidr_blocks variable. In my case, I do not want to pass in any CIDR blocks, since I use a bastion host for SSH access to the cluster. So I want to only pass in the bastion host's security group id via the allowed_inbound_security_group_ids variable.
The text was updated successfully, but these errors were encountered:
sclausson
changed the title
Support option to pass in 0 or more SSH CIDR blocks to vault-cluster module
Support option to pass in 0 or more Allowed SSH CIDR blocks to vault-cluster module
Oct 7, 2017
Currently the
vault-cluster
module requires at least 1 CIDR block to be passed in via theallowed_ssh_cidr_blocks
variable. In my case, I do not want to pass in any CIDR blocks, since I use a bastion host for SSH access to the cluster. So I want to only pass in the bastion host's security group id via theallowed_inbound_security_group_ids
variable.I've successfully tested in my fork by modifying https://github.com/hashicorp/terraform-aws-vault/blob/master/modules/vault-cluster/main.tf#L91-L99
The text was updated successfully, but these errors were encountered: