BlockDeviceMapping

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

Describes a block device mapping, which defines the EBS volumes and instance store volumes to attach to an instance at launch.

interface BlockDeviceMapping {

DeviceName?: string | null;

Ebs?: EbsBlockDevice | null;

NoDevice?: string | null;

VirtualName?: string | null;

}

§Properties

DeviceName?: string | null

[src]

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

Ebs?: EbsBlockDevice | null

[src]

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

NoDevice?: string | null

[src]

To omit the device from the block device mapping, specify an empty string. When this property is specified, the device is removed from the block device mapping regardless of the assigned value.

VirtualName?: string | null

[src]

The virtual device name (ephemeralN). Instance store volumes are numbered starting from 0. An instance type with 2 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.

NVMe instance store volumes are automatically enumerated and assigned a device name. Including them in your block device mapping has no effect.

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.