Struct aws_sdk_ec2::types::builders::BlockDeviceMappingBuilder
source · #[non_exhaustive]pub struct BlockDeviceMappingBuilder { /* private fields */ }
Expand description
A builder for BlockDeviceMapping
.
Implementations§
source§impl BlockDeviceMappingBuilder
impl BlockDeviceMappingBuilder
sourcepub fn device_name(self, input: impl Into<String>) -> Self
pub fn device_name(self, input: impl Into<String>) -> Self
The device name (for example, /dev/sdh
or xvdh
).
sourcepub fn set_device_name(self, input: Option<String>) -> Self
pub fn set_device_name(self, input: Option<String>) -> Self
The device name (for example, /dev/sdh
or xvdh
).
sourcepub fn get_device_name(&self) -> &Option<String>
pub fn get_device_name(&self) -> &Option<String>
The device name (for example, /dev/sdh
or xvdh
).
sourcepub fn virtual_name(self, input: impl Into<String>) -> Self
pub fn virtual_name(self, input: impl Into<String>) -> Self
The virtual device name (ephemeral
N). 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.
sourcepub fn set_virtual_name(self, input: Option<String>) -> Self
pub fn set_virtual_name(self, input: Option<String>) -> Self
The virtual device name (ephemeral
N). 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.
sourcepub fn get_virtual_name(&self) -> &Option<String>
pub fn get_virtual_name(&self) -> &Option<String>
The virtual device name (ephemeral
N). 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.
sourcepub fn ebs(self, input: EbsBlockDevice) -> Self
pub fn ebs(self, input: EbsBlockDevice) -> Self
Parameters used to automatically set up EBS volumes when the instance is launched.
sourcepub fn set_ebs(self, input: Option<EbsBlockDevice>) -> Self
pub fn set_ebs(self, input: Option<EbsBlockDevice>) -> Self
Parameters used to automatically set up EBS volumes when the instance is launched.
sourcepub fn get_ebs(&self) -> &Option<EbsBlockDevice>
pub fn get_ebs(&self) -> &Option<EbsBlockDevice>
Parameters used to automatically set up EBS volumes when the instance is launched.
sourcepub fn no_device(self, input: impl Into<String>) -> Self
pub fn no_device(self, input: impl Into<String>) -> Self
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.
sourcepub fn set_no_device(self, input: Option<String>) -> Self
pub fn set_no_device(self, input: Option<String>) -> Self
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.
sourcepub fn get_no_device(&self) -> &Option<String>
pub fn get_no_device(&self) -> &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.
sourcepub fn build(self) -> BlockDeviceMapping
pub fn build(self) -> BlockDeviceMapping
Consumes the builder and constructs a BlockDeviceMapping
.
Trait Implementations§
source§impl Clone for BlockDeviceMappingBuilder
impl Clone for BlockDeviceMappingBuilder
source§fn clone(&self) -> BlockDeviceMappingBuilder
fn clone(&self) -> BlockDeviceMappingBuilder
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moresource§impl Debug for BlockDeviceMappingBuilder
impl Debug for BlockDeviceMappingBuilder
source§impl Default for BlockDeviceMappingBuilder
impl Default for BlockDeviceMappingBuilder
source§fn default() -> BlockDeviceMappingBuilder
fn default() -> BlockDeviceMappingBuilder
source§impl PartialEq<BlockDeviceMappingBuilder> for BlockDeviceMappingBuilder
impl PartialEq<BlockDeviceMappingBuilder> for BlockDeviceMappingBuilder
source§fn eq(&self, other: &BlockDeviceMappingBuilder) -> bool
fn eq(&self, other: &BlockDeviceMappingBuilder) -> bool
self
and other
values to be equal, and is used
by ==
.