Interface ScheduledInstancesBlockDeviceMapping.Builder

    • Method Detail

      • deviceName

        ScheduledInstancesBlockDeviceMapping.Builder deviceName​(String deviceName)

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

        Parameters:
        deviceName - The device name (for example, /dev/sdh or xvdh).
        Returns:
        Returns a reference to this object so that method calls can be chained together.
      • ebs

        ScheduledInstancesBlockDeviceMapping.Builder ebs​(ScheduledInstancesEbs ebs)

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

        Parameters:
        ebs - Parameters used to set up EBS volumes automatically when the instance is launched.
        Returns:
        Returns a reference to this object so that method calls can be chained together.
      • noDevice

        ScheduledInstancesBlockDeviceMapping.Builder noDevice​(String noDevice)

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

        Parameters:
        noDevice - To omit the device from the block device mapping, specify an empty string.
        Returns:
        Returns a reference to this object so that method calls can be chained together.
      • virtualName

        ScheduledInstancesBlockDeviceMapping.Builder virtualName​(String 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.

        Parameters:
        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.

        Returns:
        Returns a reference to this object so that method calls can be chained together.