Skip to content

ScheduledInstancesBlockDeviceMapping

Source code in docs_src/capo_ec2/types/scheduled_instances_block_device_mapping.py 
14
15
16
17
18
19
20
21
22
class ScheduledInstancesBlockDeviceMapping(TypedDict, closed=True):
    device_name: NotRequired["capo_ec2.types.string.String"]
    """<p>The device name (for example, <code>/dev/sdh</code> or <code>xvdh</code>).</p>"""
    ebs: NotRequired["capo_ec2.types.scheduled_instances_ebs.ScheduledInstancesEbs"]
    """<p>Parameters used to set up EBS volumes automatically when the instance is launched.</p>"""
    no_device: NotRequired["capo_ec2.types.string.String"]
    """<p>To omit the device from the block device mapping, specify an empty string.</p>"""
    virtual_name: NotRequired["capo_ec2.types.string.String"]
    """<p>The virtual device name (<code>ephemeral</code>N). Instance store volumes are numbered starting from 0. An instance type with two available instance store volumes can specify mappings for <code>ephemeral0</code> and <code>ephemeral1</code>. The number of available instance store volumes depends on the instance type. After you connect to the instance, you must mount the volume.</p> <p>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.</p>"""

device_name instance-attribute 

device_name: NotRequired[String]

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

ebs instance-attribute 

ebs: NotRequired[ScheduledInstancesEbs]

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

no_device instance-attribute 

no_device: NotRequired[String]

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

virtual_name instance-attribute 

virtual_name: NotRequired[String]

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.