You are viewing documentation for version 2 of the AWS SDK for Ruby. Version 3 documentation can be found here.
Class: Aws::EC2::Types::ScheduledInstancesBlockDeviceMapping
- Inherits:
-
Struct
- Object
- Struct
- Aws::EC2::Types::ScheduledInstancesBlockDeviceMapping
- Defined in:
- (unknown)
Overview
When passing ScheduledInstancesBlockDeviceMapping as input to an Aws::Client method, you can use a vanilla Hash:
{
device_name: "String",
ebs: {
delete_on_termination: false,
encrypted: false,
iops: 1,
snapshot_id: "SnapshotId",
volume_size: 1,
volume_type: "String",
},
no_device: "String",
virtual_name: "String",
}
Describes a block device mapping for a Scheduled Instance.
Instance Attribute Summary collapse
-
#device_name ⇒ String
The device name (for example,
/dev/sdh
orxvdh
). -
#ebs ⇒ Types::ScheduledInstancesEbs
Parameters used to set up EBS volumes automatically when the instance is launched.
-
#no_device ⇒ String
Suppresses the specified device included in the block device mapping of the AMI.
-
#virtual_name ⇒ String
The virtual device name (
ephemeral
N).
Instance Attribute Details
#device_name ⇒ String
The device name (for example, /dev/sdh
or xvdh
).
#ebs ⇒ Types::ScheduledInstancesEbs
Parameters used to set up EBS volumes automatically when the instance is launched.
#no_device ⇒ String
Suppresses the specified device included in the block device mapping of the AMI.
#virtual_name ⇒ String
The virtual device name (ephemeral
N). Instance store volumes are
numbered starting from 0. An instance type with two 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.
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.