AWS CloudFormation
User Guide (Version )

The AWS Documentation website is getting a new look!
Try it now and let us know what you think. Switch to the new look >>

You can return to the original look by selecting English in the language selector above.

AWS::EC2::SpotFleet BlockDeviceMapping

Specifies a block device mapping.

You can specify Ebs or VirtualName, but not both.

Syntax

To declare this entity in your AWS CloudFormation template, use the following syntax:

JSON

{ "DeviceName" : String, "Ebs" : EbsBlockDevice, "NoDevice" : String, "VirtualName" : String }

YAML

DeviceName: String Ebs: EbsBlockDevice NoDevice: String VirtualName: String

Properties

DeviceName

The device name (for example, /dev/sdh or xvdh).

Required: Yes

Type: String

Update requires: No interruption

Ebs

Parameters used to automatically set up EBS volumes when the instance is launched.

Required: Conditional

Type: EbsBlockDevice

Update requires: No interruption

NoDevice

Suppresses the specified device included in the block device mapping of the AMI.

Required: No

Type: String

Update requires: No interruption

VirtualName

The virtual device name (ephemeralN). 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.

Required: Conditional

Type: String

Update requires: No interruption

On this page: