ScheduledInstancesBlockDeviceMapping

import type { ScheduledInstancesBlockDeviceMapping } from "https://aws-api.deno.dev/v0.3/services/ec2.ts?docs=full";

Describes a block device mapping for a Scheduled Instance.

interface ScheduledInstancesBlockDeviceMapping {

DeviceName?: string | null;

Ebs?: ScheduledInstancesEbs | null;

NoDevice?: string | null;

VirtualName?: string | null;

}

§Properties

DeviceName?: string | null

[src]

The device name (for example, /dev/sdh or xvdh).

Ebs?: ScheduledInstancesEbs | null

[src]

Parameters used to set up EBS volumes automatically when the instance is launched.

NoDevice?: string | null

[src]

To omit the device from the block device mapping, specify an empty string.

VirtualName?: string | null

[src]

The virtual device name (ephemeralN). Instance store volumes are numbered starting from 0. An instance type with two available instance store volumes can specify mappings for ephemeral0 and ephemeral1. The number of available instance store volumes depends on the instance type. After you connect to the instance, you must mount the volume.

Constraints: For M3 instances, you must specify instance store volumes in the block device mapping for the instance. When you launch an M3 instance, we ignore any instance store volumes specified in the block device mapping for the AMI.