@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class ScheduledInstancesBlockDeviceMapping extends Object implements Serializable, Cloneable
Describes a block device mapping for a Scheduled Instance.
Constructor and Description |
---|
ScheduledInstancesBlockDeviceMapping() |
Modifier and Type | Method and Description |
---|---|
ScheduledInstancesBlockDeviceMapping |
clone() |
boolean |
equals(Object obj) |
String |
getDeviceName()
The device name (for example,
/dev/sdh or xvdh ). |
ScheduledInstancesEbs |
getEbs()
Parameters used to set up EBS volumes automatically when the instance is launched.
|
String |
getNoDevice()
To omit the device from the block device mapping, specify an empty string.
|
String |
getVirtualName()
The virtual device name (
ephemeral N). |
int |
hashCode() |
void |
setDeviceName(String deviceName)
The device name (for example,
/dev/sdh or xvdh ). |
void |
setEbs(ScheduledInstancesEbs ebs)
Parameters used to set up EBS volumes automatically when the instance is launched.
|
void |
setNoDevice(String noDevice)
To omit the device from the block device mapping, specify an empty string.
|
void |
setVirtualName(String virtualName)
The virtual device name (
ephemeral N). |
String |
toString()
Returns a string representation of this object.
|
ScheduledInstancesBlockDeviceMapping |
withDeviceName(String deviceName)
The device name (for example,
/dev/sdh or xvdh ). |
ScheduledInstancesBlockDeviceMapping |
withEbs(ScheduledInstancesEbs ebs)
Parameters used to set up EBS volumes automatically when the instance is launched.
|
ScheduledInstancesBlockDeviceMapping |
withNoDevice(String noDevice)
To omit the device from the block device mapping, specify an empty string.
|
ScheduledInstancesBlockDeviceMapping |
withVirtualName(String virtualName)
The virtual device name (
ephemeral N). |
public ScheduledInstancesBlockDeviceMapping()
public void setDeviceName(String deviceName)
The device name (for example, /dev/sdh
or xvdh
).
deviceName
- The device name (for example, /dev/sdh
or xvdh
).public String getDeviceName()
The device name (for example, /dev/sdh
or xvdh
).
/dev/sdh
or xvdh
).public ScheduledInstancesBlockDeviceMapping withDeviceName(String deviceName)
The device name (for example, /dev/sdh
or xvdh
).
deviceName
- The device name (for example, /dev/sdh
or xvdh
).public void setEbs(ScheduledInstancesEbs ebs)
Parameters used to set up EBS volumes automatically when the instance is launched.
ebs
- Parameters used to set up EBS volumes automatically when the instance is launched.public ScheduledInstancesEbs getEbs()
Parameters used to set up EBS volumes automatically when the instance is launched.
public ScheduledInstancesBlockDeviceMapping withEbs(ScheduledInstancesEbs ebs)
Parameters used to set up EBS volumes automatically when the instance is launched.
ebs
- Parameters used to set up EBS volumes automatically when the instance is launched.public void setNoDevice(String noDevice)
To omit the device from the block device mapping, specify an empty string.
noDevice
- To omit the device from the block device mapping, specify an empty string.public String getNoDevice()
To omit the device from the block device mapping, specify an empty string.
public ScheduledInstancesBlockDeviceMapping withNoDevice(String noDevice)
To omit the device from the block device mapping, specify an empty string.
noDevice
- To omit the device from the block device mapping, specify an empty string.public void setVirtualName(String virtualName)
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.
virtualName
- 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.
public String getVirtualName()
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.
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.
public ScheduledInstancesBlockDeviceMapping withVirtualName(String virtualName)
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.
virtualName
- 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.
public String toString()
toString
in class Object
Object.toString()
public ScheduledInstancesBlockDeviceMapping clone()