ScheduledInstancesLaunchSpecification
import type { ScheduledInstancesLaunchSpecification } from "https://aws-api.deno.dev/v0.3/services/ec2.ts?docs=full";Describes the launch specification for a Scheduled Instance.
If you are launching the Scheduled Instance in EC2-VPC, you must specify the ID of the subnet.
You can specify the subnet using either SubnetId or NetworkInterface.
interface ScheduledInstancesLaunchSpecification {
BlockDeviceMappings?: ScheduledInstancesBlockDeviceMapping[] | null;
EbsOptimized?: boolean | null;
IamInstanceProfile?: ScheduledInstancesIamInstanceProfile | null;
ImageId: string;
InstanceType?: string | null;
KernelId?: string | null;
KeyName?: string | null;
Monitoring?: ScheduledInstancesMonitoring | null;
NetworkInterfaces?: ScheduledInstancesNetworkInterface[] | null;
Placement?: ScheduledInstancesPlacement | null;
RamdiskId?: string | null;
SecurityGroupIds?: string[] | null;
SubnetId?: string | null;
UserData?: string | null;
}§Properties
§
BlockDeviceMappings?: ScheduledInstancesBlockDeviceMapping[] | null
[src]The block device mapping entries.
§
EbsOptimized?: boolean | null
[src]Indicates whether the instances are optimized for EBS I/O. This optimization provides dedicated throughput to Amazon EBS and an optimized configuration stack to provide optimal EBS I/O performance. This optimization isn't available with all instance types. Additional usage charges apply when using an EBS-optimized instance.
Default: false
§
IamInstanceProfile?: ScheduledInstancesIamInstanceProfile | null
[src]The IAM instance profile.
§
Monitoring?: ScheduledInstancesMonitoring | null
[src]Enable or disable monitoring for the instances.
§
NetworkInterfaces?: ScheduledInstancesNetworkInterface[] | null
[src]The network interfaces.
§
Placement?: ScheduledInstancesPlacement | null
[src]The placement information.