public static interface BlockDeviceMapping.Builder extends SdkPojo, CopyableBuilder<BlockDeviceMapping.Builder,BlockDeviceMapping>
Modifier and Type | Method and Description |
---|---|
BlockDeviceMapping.Builder |
deviceName(String deviceName)
The device name (for example,
/dev/sdh or xvdh ). |
default BlockDeviceMapping.Builder |
ebs(Consumer<EbsBlockDevice.Builder> ebs)
Parameters used to automatically set up EBS volumes when the instance is launched.
|
BlockDeviceMapping.Builder |
ebs(EbsBlockDevice ebs)
Parameters used to automatically set up EBS volumes when the instance is launched.
|
BlockDeviceMapping.Builder |
noDevice(String noDevice)
Suppresses the specified device included in the block device mapping of the AMI.
|
BlockDeviceMapping.Builder |
virtualName(String virtualName)
The virtual device name (
ephemeral N). |
equalsBySdkFields, sdkFields
copy
applyMutation, build
BlockDeviceMapping.Builder deviceName(String deviceName)
The device name (for example, /dev/sdh
or xvdh
).
deviceName
- The device name (for example, /dev/sdh
or xvdh
).BlockDeviceMapping.Builder virtualName(String 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.
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.
BlockDeviceMapping.Builder ebs(EbsBlockDevice ebs)
Parameters used to automatically set up EBS volumes when the instance is launched.
ebs
- Parameters used to automatically set up EBS volumes when the instance is launched.default BlockDeviceMapping.Builder ebs(Consumer<EbsBlockDevice.Builder> ebs)
Parameters used to automatically set up EBS volumes when the instance is launched.
This is a convenience that creates an instance of theEbsBlockDevice.Builder
avoiding the need to
create one manually via EbsBlockDevice.builder()
.
When the Consumer
completes, SdkBuilder.build()
is called immediately and its
result is passed to ebs(EbsBlockDevice)
.ebs
- a consumer that will call methods on EbsBlockDevice.Builder
ebs(EbsBlockDevice)
BlockDeviceMapping.Builder noDevice(String noDevice)
Suppresses the specified device included in the block device mapping of the AMI.
noDevice
- Suppresses the specified device included in the block device mapping of the AMI.Copyright © 2019. All rights reserved.