Properties of the bastion host.
|vpc||VPC to launch the instance in.|
|availability||In which AZ to place the instance within the VPC.|
|block||Specifies how block devices are exposed to the instance. You can specify virtual devices and EBS volumes.|
|instance||The name of the instance.|
|instance||Type of instance to launch.|
|machine||The machine image to use.|
|security||Security Group to assign to this instance.|
|subnet||Select the subnets to run the bastion host in.|
VPC to launch the instance in.
(optional, default: Random zone.)
In which AZ to place the instance within the VPC.
(optional, default: Uses the block device mapping of the AMI)
Specifies how block devices are exposed to the instance. You can specify virtual devices and EBS volumes.
Each instance that is launched has an associated root device volume, either an Amazon EBS volume or an instance store volume. You can use block device mappings to specify additional EBS volumes or instance store volumes to attach to an instance when it is launched.
(optional, default: 'BastionHost')
The name of the instance.
(optional, default: 't3.nano')
Type of instance to launch.
(optional, default: An Amazon Linux 2 image which is kept up-to-date automatically (the instance
may be replaced on every deployment).)
The machine image to use.
(optional, default: create new security group with no inbound and all outbound traffic allowed)
Security Group to assign to this instance.
(optional, default: private subnets of the supplied VPC)
Select the subnets to run the bastion host in.
Set this to PUBLIC if you need to connect to this instance via the internet and cannot use SSM. You have to allow port 22 manually by using the connections field