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 Oct 4, 2024. It is now read-only.
I don't need to access my bastion externally. My VPN gives me access to my VPCs private subnet but the public subnet requires the bastion. I deploy to the private subnets and it works fine, but it's assigning a public IP still. I don't think it's a risk but would be nice to expose a parameter to not assign a public IP.
Then it may make sense to rename PublicSubnet1ID/PublicSubnet2ID to just Subnet#ID and add a note in the docs.
The text was updated successfully, but these errors were encountered:
supergibbs
added a commit
to supergibbs/quickstart-linux-bastion
that referenced
this issue
May 1, 2023
I don't need to access my bastion externally. My VPN gives me access to my VPCs private subnet but the public subnet requires the bastion. I deploy to the private subnets and it works fine, but it's assigning a public IP still. I don't think it's a risk but would be nice to expose a parameter to not assign a public IP.
Then it may make sense to rename
PublicSubnet1ID/PublicSubnet2ID
to justSubnet#ID
and add a note in the docs.The text was updated successfully, but these errors were encountered: