Struct aws_sdk_ec2::model::ScheduledInstancesBlockDeviceMapping

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

Describes a block device mapping for a Scheduled Instance.

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).

ebs: Option<ScheduledInstancesEbs>

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

no_device: Option<String>

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

virtual_name: Option<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.

Implementations

impl ScheduledInstancesBlockDeviceMapping

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

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

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

Parameters used to set up EBS volumes automatically 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.

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

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.

impl ScheduledInstancesBlockDeviceMapping

pub fn builder() -> Builder

Creates a new builder-style object to manufacture ScheduledInstancesBlockDeviceMapping

Trait Implementations

impl Clone for ScheduledInstancesBlockDeviceMapping

fn clone(&self) -> ScheduledInstancesBlockDeviceMapping

Returns a copy of the value.

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

Performs copy-assignment from source.

impl Debug for ScheduledInstancesBlockDeviceMapping

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

Formats the value using the given formatter.

impl PartialEq<ScheduledInstancesBlockDeviceMapping> for ScheduledInstancesBlockDeviceMapping

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

This method tests for self and other values to be equal, and is used by ==.

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

This method tests for !=.

impl StructuralPartialEq for ScheduledInstancesBlockDeviceMapping