Bastion deployment to a specific VPC

[petabook]

This is probably a stupid question, but how do I deploy the aws-bastion to a VPC other than "vpc"? i.e., my VPC is named "mgmt".

[Benbentwo]

Hey @petabook, no stupid questions, so the bastion component uses a remote state lookup of a component called vpc (by name) in the remote-state.tf file.

The reason we do it this way is out of convention; we want one VPC account to define the account and network boundaries clearly. By having our components lookup the VPC we define it helps ensure nothing is deployed elsewhere that could blur the lines on those boundaries. Admittedly - the way this is currently setup with a hardcoded "VPC" is not very flexible and could be updated to use a vpc_component_name variable that defaults to "vpc".

We're open to pull requests, on the other hand you can always add a remote_state_override.tf file that would change how it looks it up.

https://developer.hashicorp.com/terraform/language/files/override

[Benbentwo]

Supported this via cloudposse-terraform-components/aws-bastion#29

You can update the component.yaml to the latest version v1.536.1