Copyright | (c) 2013-2023 Brendan Hay |
---|---|
License | Mozilla Public License, v. 2.0. |
Maintainer | Brendan Hay |
Stability | auto-generated |
Portability | non-portable (GHC extensions) |
Safe Haskell | Safe-Inferred |
Language | Haskell2010 |
Synopsis
- data BlockDeviceMapping = BlockDeviceMapping' {
- ebs :: Maybe EbsBlockDevice
- noDevice :: Maybe Text
- virtualName :: Maybe Text
- deviceName :: Text
- newBlockDeviceMapping :: Text -> BlockDeviceMapping
- blockDeviceMapping_ebs :: Lens' BlockDeviceMapping (Maybe EbsBlockDevice)
- blockDeviceMapping_noDevice :: Lens' BlockDeviceMapping (Maybe Text)
- blockDeviceMapping_virtualName :: Lens' BlockDeviceMapping (Maybe Text)
- blockDeviceMapping_deviceName :: Lens' BlockDeviceMapping Text
Documentation
data BlockDeviceMapping Source #
Describes a block device mapping, which defines the EBS volumes and instance store volumes to attach to an instance at launch.
See: newBlockDeviceMapping
smart constructor.
BlockDeviceMapping' | |
|
Instances
newBlockDeviceMapping Source #
Create a value of BlockDeviceMapping
with all optional fields omitted.
Use generic-lens or optics to modify other optional fields.
The following record fields are available, with the corresponding lenses provided for backwards compatibility:
$sel:ebs:BlockDeviceMapping'
, blockDeviceMapping_ebs
- Parameters used to automatically set up EBS volumes when the instance is
launched.
$sel:noDevice:BlockDeviceMapping'
, blockDeviceMapping_noDevice
- 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.
$sel:virtualName:BlockDeviceMapping'
, blockDeviceMapping_virtualName
- 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.
$sel:deviceName:BlockDeviceMapping'
, blockDeviceMapping_deviceName
- The device name (for example, /dev/sdh
or xvdh
).
blockDeviceMapping_ebs :: Lens' BlockDeviceMapping (Maybe EbsBlockDevice) Source #
Parameters used to automatically set up EBS volumes when the instance is launched.
blockDeviceMapping_noDevice :: Lens' BlockDeviceMapping (Maybe Text) Source #
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.
blockDeviceMapping_virtualName :: Lens' BlockDeviceMapping (Maybe Text) Source #
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.
blockDeviceMapping_deviceName :: Lens' BlockDeviceMapping Text Source #
The device name (for example, /dev/sdh
or xvdh
).