Interface CfnSpotFleet.IBlockDeviceMappingProperty
Specifies a block device mapping.
Namespace: Amazon.CDK.AWS.EC2
Assembly: Amazon.CDK.Lib.dll
Syntax (csharp)
public interface IBlockDeviceMappingProperty
Syntax (vb)
Public Interface IBlockDeviceMappingProperty
Remarks
You can specify Ebs
or VirtualName
, but not both.
ExampleMetadata: fixture=_generated
Examples
// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
using Amazon.CDK.AWS.EC2;
var blockDeviceMappingProperty = new BlockDeviceMappingProperty {
DeviceName = "deviceName",
// the properties below are optional
Ebs = new EbsBlockDeviceProperty {
DeleteOnTermination = false,
Encrypted = false,
Iops = 123,
SnapshotId = "snapshotId",
VolumeSize = 123,
VolumeType = "volumeType"
},
NoDevice = "noDevice",
VirtualName = "virtualName"
};
Synopsis
Properties
DeviceName | The device name (for example, |
Ebs | Parameters used to automatically set up EBS volumes when the instance is launched. |
NoDevice | To omit the device from the block device mapping, specify an empty string. |
VirtualName | The virtual device name ( |
Properties
DeviceName
The device name (for example, /dev/sdh
or xvdh
).
string DeviceName { get; }
Property Value
System.String
Remarks
Ebs
Parameters used to automatically set up EBS volumes when the instance is launched.
virtual object Ebs { get; }
Property Value
System.Object
Remarks
NoDevice
To omit the device from the block device mapping, specify an empty string.
virtual string NoDevice { get; }
Property Value
System.String
Remarks
When this property is specified, the device is removed from the block device mapping regardless of the assigned value.
VirtualName
The virtual device name ( ephemeral
N).
virtual string VirtualName { get; }
Property Value
System.String
Remarks
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.