Interface CfnSpotFleet.BlockDeviceMappingProperty
- All Superinterfaces:
software.amazon.jsii.JsiiSerializable
- All Known Implementing Classes:
CfnSpotFleet.BlockDeviceMappingProperty.Jsii$Proxy
- Enclosing class:
CfnSpotFleet
You can specify Ebs
or VirtualName
, but not both.
Example:
// The code below shows an example of how to instantiate this type. // The values are placeholders you should change. import software.amazon.awscdk.services.ec2.*; BlockDeviceMappingProperty blockDeviceMappingProperty = BlockDeviceMappingProperty.builder() .deviceName("deviceName") // the properties below are optional .ebs(EbsBlockDeviceProperty.builder() .deleteOnTermination(false) .encrypted(false) .iops(123) .snapshotId("snapshotId") .volumeSize(123) .volumeType("volumeType") .build()) .noDevice("noDevice") .virtualName("virtualName") .build();
-
Nested Class Summary
Modifier and TypeInterfaceDescriptionstatic final class
A builder forCfnSpotFleet.BlockDeviceMappingProperty
static final class
An implementation forCfnSpotFleet.BlockDeviceMappingProperty
-
Method Summary
Modifier and TypeMethodDescriptionbuilder()
The device name (for example,/dev/sdh
orxvdh
).default Object
getEbs()
Parameters used to automatically set up EBS volumes when the instance is launched.default String
To omit the device from the block device mapping, specify an empty string.default String
The virtual device name (ephemeral
N).Methods inherited from interface software.amazon.jsii.JsiiSerializable
$jsii$toJson
-
Method Details
-
getDeviceName
The device name (for example,/dev/sdh
orxvdh
). -
getEbs
Parameters used to automatically set up EBS volumes when the instance is launched. -
getNoDevice
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.
-
getVirtualName
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
andephemeral1
. 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.
-
builder
-