The Launch EC2 Scheduled Instances action can be used to start one or more scheduled instances. Once the instances have been started, they can be optionally terminated after they have been running for a specific amount of time.
Please see Common Action Settings for a description of settings common to all action types.
Scheduled Instance Identification Method
Indicates the method with which scheduled instances are selected to be launched. Possible choices include:
- All Scheduled Instances
- By Scheduled Instance ID
Scheduled Instance IDs
Required when "Scheduled Instance Identification Method" is set to "By Scheduled Instance ID". Specifies the unique IDs of the scheduled instances that are to be launched.
Indicate the image ID of your AMI image. This value usually looks like "ami-84a3dc7b". This image must reside in the region specified.
VPC Subnet ID
Optional. Indicates the ID of the subnet to launch the instances into. This used when using Amazon Virtual Private Cloud.
Optional. Indicates the security group to assign to the new instances. This value usually looks like "sg-84a3dc7b". If no security group is specified, the "default" security group is used.
Key Pair Name
Optional. Name of the key pair used for SSH access and administrator password decryption.
IAM Instance Profile
Optional. Name of the IAM instance profile with which the new EC2 instances should run.
Optional. Specify user data to help configure your instances.
User Data Format
Format of the user data. Possible options include:
- Base-64 Encoded
Optional. Additional EC2 tags can be added to the launched EC2 instances. Specify those tags here. Macros can be used to include runtime information.
Maximum Instance Count
Optional. Indicates the maximum number of spot requests.
Terminate the Instances
If the instances should be terminated, enable this option.
Time Before Termination
If the instances should be terminated automatically, specify the length of time the instances are to stay running before they are terminated.
Amazon Commands Used
The following Amazon AWS commands are used. The access key should have permission to execute all of them.