Properties of an EC2 Instance.
|instance||Type of instance to launch.|
|machine||AMI to launch.|
|vpc||VPC to launch the instance in.|
|allow||Whether the instance could initiate connections to anywhere by default.|
|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.|
|init?||Apply the given CloudFormation Init configuration to the instance at startup.|
|init||Use the given options for applying CloudFormation Init.|
|instance||The name of the instance.|
|key||Name of SSH keypair to grant access to instance.|
|private||Defines a private IP address to associate with an instance.|
|resource||The length of time to wait for the resourceSignalCount.|
|role?||An IAM role to associate with the instance profile assigned to this Auto Scaling Group.|
|security||Security Group to assign to this instance.|
|source||Specifies whether to enable an instance launched in a VPC to perform NAT.|
|user||Specific UserData to use.|
|user||Changes to the UserData force replacement.|
|vpc||Where to place the instance within the VPC.|
Type of instance to launch.
AMI to launch.
VPC to launch the instance in.
(optional, default: true)
Whether the instance could initiate connections to anywhere by default.
This property is only used when you do not provide a security group.
(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: no CloudFormation init)
Apply the given CloudFormation Init configuration to the instance at startup.
(optional, default: default options)
Use the given options for applying CloudFormation Init.
Describes the configsets to use and the timeout to wait
(optional, default: CDK generated name)
The name of the instance.
(optional, default: No SSH access will be possible.)
Name of SSH keypair to grant access to instance.
(optional, default: no association)
Defines a private IP address to associate with an instance.
Private IP should be available within the VPC that the instance is build within.
(optional, default: Duration.minutes(5))
The length of time to wait for the resourceSignalCount.
The maximum value is 43200 (12 hours).
(optional, default: A role will automatically be created, it can be accessed via the
An IAM role to associate with the instance profile assigned to this Auto Scaling Group.
The role must be assumable by the service principal
(optional, default: create new security group)
Security Group to assign to this instance.
(optional, default: true)
Specifies whether to enable an instance launched in a VPC to perform NAT.
This controls whether source/destination checking is enabled on the instance. A value of true means that checking is enabled, and false means that checking is disabled. The value must be false for the instance to perform NAT.
(optional, default: A UserData object appropriate for the MachineImage's
Operating System is created.)
Specific UserData to use.
The UserData may still be mutated after creation.
(optional, default: true iff
initOptions is specified, false otherwise.)
Changes to the UserData force replacement.
Depending the EC2 instance type, changing UserData either restarts the instance or replaces the instance.
- Instance store-backed instances are replaced.
- EBS-backed instances are restarted.
By default, restarting does not execute the new UserData so you will need a different mechanism to ensure the instance is restarted.
Setting this to
true will make the instance's Logical ID depend on the
UserData, which will cause CloudFormation to replace it if the UserData
(optional, default: Private subnets.)
Where to place the instance within the VPC.