Struct FleetBlockDeviceMappingRequest

#[non_exhaustive]
pub struct FleetBlockDeviceMappingRequest {
    pub device_name: Option<String>,
    pub virtual_name: Option<String>,
    pub ebs: Option<FleetEbsBlockDeviceRequest>,
    pub no_device: Option<String>,
}

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

To override a block device mapping specified in the launch template:

• Specify the exact same DeviceName here as specified in the launch template.

• Only specify the parameters you want to change.

• Any parameters you don't specify here will keep their original launch template values.

To add a new block device mapping:

• Specify a DeviceName that doesn't exist in the launch template.

• Specify all desired parameters here.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

device_name: Option<String>

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

virtual_name: Option<String>

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.

ebs: Option<FleetEbsBlockDeviceRequest>

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

no_device: Option<String>

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.

Implementations

impl FleetBlockDeviceMappingRequest

pub fn device_name(&self) -> Option<&str>

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

pub fn virtual_name(&self) -> Option<&str>

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.

pub fn ebs(&self) -> Option<&FleetEbsBlockDeviceRequest>

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

pub fn no_device(&self) -> Option<&str>

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.

impl FleetBlockDeviceMappingRequest

pub fn builder() -> FleetBlockDeviceMappingRequestBuilder

Creates a new builder-style object to manufacture FleetBlockDeviceMappingRequest.

Trait Implementations

impl Clone for FleetBlockDeviceMappingRequest

fn clone(&self) -> FleetBlockDeviceMappingRequest

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for FleetBlockDeviceMappingRequest

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq for FleetBlockDeviceMappingRequest

fn eq(&self, other: &FleetBlockDeviceMappingRequest) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for FleetBlockDeviceMappingRequest