interface BlockDeviceMappingProperty
Language | Type name |
---|---|
.NET | Amazon.CDK.AWS.EC2.CfnSpotFleet.BlockDeviceMappingProperty |
Java | software.amazon.awscdk.services.ec2.CfnSpotFleet.BlockDeviceMappingProperty |
Python | aws_cdk.aws_ec2.CfnSpotFleet.BlockDeviceMappingProperty |
TypeScript | @aws-cdk/aws-ec2 » CfnSpotFleet » BlockDeviceMappingProperty |
Specifies a block device mapping.
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 * as ec2 from '@aws-cdk/aws-ec2';
const blockDeviceMappingProperty: ec2.CfnSpotFleet.BlockDeviceMappingProperty = {
deviceName: 'deviceName',
// the properties below are optional
ebs: {
deleteOnTermination: false,
encrypted: false,
iops: 123,
snapshotId: 'snapshotId',
volumeSize: 123,
volumeType: 'volumeType',
},
noDevice: 'noDevice',
virtualName: 'virtualName',
};
Properties
Name | Type | Description |
---|---|---|
device | string | The device name (for example, /dev/sdh or xvdh ). |
ebs? | IResolvable | Ebs | Parameters used to automatically set up EBS volumes when the instance is launched. |
no | string | To omit the device from the block device mapping, specify an empty string. |
virtual | string | The virtual device name ( ephemeral N). |
deviceName
Type:
string
The device name (for example, /dev/sdh
or xvdh
).
ebs?
Type:
IResolvable
|
Ebs
(optional)
Parameters used to automatically set up EBS volumes when the instance is launched.
noDevice?
Type:
string
(optional)
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.
virtualName?
Type:
string
(optional)
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.