BastionHostLinux

VPC to launch the instance in.

In which AZ to place the instance within the VPC.

Default: - Random zone.

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.

Default: - Uses the block device mapping of the AMI

Apply the given CloudFormation Init configuration to the instance at startup.

Default: - no CloudFormation init

Use the given options for applying CloudFormation Init. Describes the configsets to use and the timeout to wait

Default: - default options

The name of the instance.

Default: 'BastionHost'

Type of instance to launch.

Default: 't3.nano'

The machine image to use, assumed to have SSM Agent preinstalled.

Default: - An Amazon Linux 2023 image if the `@aws-cdk/aws-ec2:bastionHostUseAmazonLinux2023ByDefault` feature flag is enabled. Otherwise, an Amazon Linux 2 image. In both cases, the image is kept up-to-date automatically (the instance may be replaced on every deployment) and already has SSM Agent installed.

Whether IMDSv2 should be required on this instance.

Default: - false

Security Group to assign to this instance.

Default: - create new security group with no inbound and all outbound traffic allowed

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

Default: - private subnets of the supplied VPC

Determines whether changes to the UserData will force instance replacement. Depending on the EC2 instance type, modifying the UserData may either restart or replace the instance: - Instance store-backed instances are replaced. - EBS-backed instances are restarted. Note that by default, restarting does not execute the updated UserData, so an alternative mechanism is needed to ensure the instance re-executes the UserData. When set to `true`, the instance's Logical ID will depend on the UserData, causing CloudFormation to replace the instance if the UserData changes.

Default: - `true` if `initOptions` is specified, otherwise `false`.