@Generated(value="software.amazon.awssdk:codegen") public final class BlockDeviceMapping extends Object implements SdkPojo, Serializable, ToCopyableBuilder<BlockDeviceMapping.Builder,BlockDeviceMapping>
Describes a block device mapping.
Modifier and Type | Class and Description |
---|---|
static interface |
BlockDeviceMapping.Builder |
Modifier and Type | Method and Description |
---|---|
static BlockDeviceMapping.Builder |
builder() |
String |
deviceName()
The device name (for example,
/dev/sdh or xvdh ). |
EbsBlockDevice |
ebs()
Parameters used to automatically set up EBS volumes when the instance is launched.
|
boolean |
equals(Object obj) |
<T> Optional<T> |
getValueForField(String fieldName,
Class<T> clazz) |
int |
hashCode() |
String |
noDevice()
Suppresses the specified device included in the block device mapping of the AMI.
|
List<SdkField<?>> |
sdkFields() |
static Class<? extends BlockDeviceMapping.Builder> |
serializableBuilderClass() |
BlockDeviceMapping.Builder |
toBuilder()
Take this object and create a builder that contains all of the current property values of this object.
|
String |
toString() |
String |
virtualName()
The virtual device name (
ephemeral N). |
copy
public String deviceName()
The device name (for example, /dev/sdh
or xvdh
).
/dev/sdh
or xvdh
).public 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.
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.
public EbsBlockDevice ebs()
Parameters used to automatically set up EBS volumes when the instance is launched.
public String noDevice()
Suppresses the specified device included in the block device mapping of the AMI.
public BlockDeviceMapping.Builder toBuilder()
ToCopyableBuilder
toBuilder
in interface ToCopyableBuilder<BlockDeviceMapping.Builder,BlockDeviceMapping>
public static BlockDeviceMapping.Builder builder()
public static Class<? extends BlockDeviceMapping.Builder> serializableBuilderClass()
Copyright © 2017 Amazon Web Services, Inc. All Rights Reserved.