Connecting to a Volume

For volumes attached with Paravirtualized as the volume attachment type, you do not need to perform any additional steps after Attaching a Volume, the volumes are connected automatically. However, for Linux-based images, if you want to mount these volumes on instance boot, you need to perform additional configuration steps. If you specified a device path when you attached the volume, see fstab Options for Block Volumes Using Consistent Device Paths. If you did not specify a device path or if your instance was created from an image that does not support device paths, see Traditional fstab Options.

For volumes attached with iSCSI as the volume attachment type, you need to connect and mount the volume from the instance for the volume to be usable. For more information about attachment type options, see Volume Attachment Types. In order to connect the volume, you must first attach  the volume to the instance, see Attaching a Volume.

Connecting to iSCSI-Attached Volumes

Required IAM Policy

Connecting a volume to an instance does not require a specific IAM policy. However, you may need permission to run the necessary commands on the instance's guest OS. Contact your system administrator for more information.


You must attach the volume to the instance before you can connect the volume to the instance's guest OS. For details, see Attaching a Volume.

To connect the volume, you need the following information:

  • iSCSI IP Address
  • iSCSI Port numbers
  • CHAP  credentials (if you enabled CHAP)
  • IQN 

The Console provides the commands required to configure, authenticate, and log on to iSCSI.

Connecting to a Volume on a Linux Instance
Connecting to a Volume on a Windows Instance