amazonka-ec2-2.0: Amazon Elastic Compute Cloud SDK.
Copyright(c) 2013-2023 Brendan Hay
LicenseMozilla Public License, v. 2.0.
MaintainerBrendan Hay
Stabilityauto-generated
Portabilitynon-portable (GHC extensions)
Safe HaskellSafe-Inferred
LanguageHaskell2010

Amazonka.EC2.Types.ScheduledInstancesBlockDeviceMapping

Description

 
Synopsis

Documentation

data ScheduledInstancesBlockDeviceMapping Source #

Describes a block device mapping for a Scheduled Instance.

See: newScheduledInstancesBlockDeviceMapping smart constructor.

Constructors

ScheduledInstancesBlockDeviceMapping' 

Fields

  • deviceName :: Maybe Text

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

  • ebs :: Maybe ScheduledInstancesEbs

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

  • noDevice :: Maybe Text

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

  • virtualName :: Maybe Text

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

Instances

Instances details
ToQuery ScheduledInstancesBlockDeviceMapping Source # 
Instance details

Defined in Amazonka.EC2.Types.ScheduledInstancesBlockDeviceMapping

Generic ScheduledInstancesBlockDeviceMapping Source # 
Instance details

Defined in Amazonka.EC2.Types.ScheduledInstancesBlockDeviceMapping

Read ScheduledInstancesBlockDeviceMapping Source # 
Instance details

Defined in Amazonka.EC2.Types.ScheduledInstancesBlockDeviceMapping

Show ScheduledInstancesBlockDeviceMapping Source # 
Instance details

Defined in Amazonka.EC2.Types.ScheduledInstancesBlockDeviceMapping

NFData ScheduledInstancesBlockDeviceMapping Source # 
Instance details

Defined in Amazonka.EC2.Types.ScheduledInstancesBlockDeviceMapping

Eq ScheduledInstancesBlockDeviceMapping Source # 
Instance details

Defined in Amazonka.EC2.Types.ScheduledInstancesBlockDeviceMapping

Hashable ScheduledInstancesBlockDeviceMapping Source # 
Instance details

Defined in Amazonka.EC2.Types.ScheduledInstancesBlockDeviceMapping

type Rep ScheduledInstancesBlockDeviceMapping Source # 
Instance details

Defined in Amazonka.EC2.Types.ScheduledInstancesBlockDeviceMapping

type Rep ScheduledInstancesBlockDeviceMapping = D1 ('MetaData "ScheduledInstancesBlockDeviceMapping" "Amazonka.EC2.Types.ScheduledInstancesBlockDeviceMapping" "amazonka-ec2-2.0-48L9RAJvmvzAdBkRegqWCL" 'False) (C1 ('MetaCons "ScheduledInstancesBlockDeviceMapping'" 'PrefixI 'True) ((S1 ('MetaSel ('Just "deviceName") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe Text)) :*: S1 ('MetaSel ('Just "ebs") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe ScheduledInstancesEbs))) :*: (S1 ('MetaSel ('Just "noDevice") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe Text)) :*: S1 ('MetaSel ('Just "virtualName") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe Text)))))

newScheduledInstancesBlockDeviceMapping :: ScheduledInstancesBlockDeviceMapping Source #

Create a value of ScheduledInstancesBlockDeviceMapping with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:deviceName:ScheduledInstancesBlockDeviceMapping', scheduledInstancesBlockDeviceMapping_deviceName - The device name (for example, /dev/sdh or xvdh).

$sel:ebs:ScheduledInstancesBlockDeviceMapping', scheduledInstancesBlockDeviceMapping_ebs - Parameters used to set up EBS volumes automatically when the instance is launched.

$sel:noDevice:ScheduledInstancesBlockDeviceMapping', scheduledInstancesBlockDeviceMapping_noDevice - To omit the device from the block device mapping, specify an empty string.

$sel:virtualName:ScheduledInstancesBlockDeviceMapping', scheduledInstancesBlockDeviceMapping_virtualName - The virtual device name (ephemeralN). 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.

scheduledInstancesBlockDeviceMapping_ebs :: Lens' ScheduledInstancesBlockDeviceMapping (Maybe ScheduledInstancesEbs) Source #

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

scheduledInstancesBlockDeviceMapping_noDevice :: Lens' ScheduledInstancesBlockDeviceMapping (Maybe Text) Source #

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

scheduledInstancesBlockDeviceMapping_virtualName :: Lens' ScheduledInstancesBlockDeviceMapping (Maybe Text) Source #

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