InstanceBlockDeviceMappingArgs

data class InstanceBlockDeviceMappingArgs(val deviceName: Output<String>, val ebs: Output<InstanceEbsArgs>? = null, val noDevice: Output<Any>? = null, val virtualName: Output<String>? = null) : ConvertibleToJava<InstanceBlockDeviceMappingArgs>

Constructors

Link copied to clipboard
constructor(deviceName: Output<String>, ebs: Output<InstanceEbsArgs>? = null, noDevice: Output<Any>? = null, virtualName: Output<String>? = null)

Properties

Link copied to clipboard
val deviceName: Output<String>

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

Link copied to clipboard
val ebs: Output<InstanceEbsArgs>? = null

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

Link copied to clipboard
val noDevice: Output<Any>? = null

To omit the device from the block device mapping, specify an empty string.

Link copied to clipboard
val virtualName: Output<String>? = null

The virtual device name ( ephemeral N). The name must be in the form ephemeral X where X is a number starting from zero (0). For example, 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.

Functions

Link copied to clipboard
open override fun toJava(): InstanceBlockDeviceMappingArgs