Attach a block volume to a compute instance to expand the available storage on the
instance.
If you specify iSCSI as the
volume attachment type, you must also connect and mount the volume from the instance
for the volume to be usable. For more information, see Volume Attachment Types and
Connecting to a Block Volume.
When you change the performance for a volume, the volume's lifecycle state
changes to Provisioning while the settings are being updated. During this
process, you can't attach the volume to an instance. You must wait until the
volume's lifecycle state transitions back to Available before you attach the
volume to an instance.
Attaching Ultra High Performance Volumes
When you attach a volume configured for the Ultra High Performance level, the
volume attachment must be enabled for multipath to optimize the volume's
performance.
The Block Volume service attempts to configure the attachment as multipath-enabled during
the attachment process. After you attach a volume, you can confirm if the volume
attachment was successfully enabled for multipath. See Checking if a Volume Attachment is Multipath-Enabled.
Whether an attachment is enabled for multipath is determined based the attached
instance's shape, along with whether all the applicable prerequisites are met and
configured correctly. For more information about prerequisites and requirements for
multipath-enabled attachments, see Configuring Attachments to Ultra High Performance Volumes.
Security Zones ensure that your cloud resources comply with Oracle security principles. If any operation on a resource in a security zone compartment violates a policy for that security zone, then the operation is denied.
The following security zone policies affect your ability to attach block volumes to compute instances.
All block volumes attached to a compute instance in a security zone must be in the same security zone.
Block volumes in a security zone can't be attached to a compute instance that is
not in the same security zone.
Open the navigation menu and click Compute. Under Compute, click Instances.
Under List scope, select the compartment that contains the
instance.
In the Instances list, click the name of the instance that you want to
attach a volume to.
In the Resources, click Attached block volumes.
Click Attach block volume.
Specify the volume that you want to attach to the instance.
To use the volume name, select Select volume and
then select the volume from the Volume list. If
the volume is in a different compartment from the instance, click
Change compartment and select the compartment
that the volume is located in.
To specify the volume OCID, select Enter volume
OCID and then enter the OCID into the Volume
OCID field
If the instance supports consistent device paths, and the volume that you're
attaching is not a boot volume, select a path from the Device path list.
This feature enables you to specify a device path for the volume attachment that
remains consistent between instance reboots.
For iSCSI volume attachments, optionally require CHAP credentials by selecting
the Require CHAP credentials check box.
For iSCSI attachments to Linux-based instances, you can also optionally configure
the attachment to use the Block Volume Management plugin to run the
iSCSI commands to automatically connect to the volume. To do this, select the
Use Oracle Cloud Agent to automatically connect to iSCSI-attached
volumes check box.
Important
To automatically connect to the volume, the Block Volume Management plugin must be
enabled on the instance. See Enabling the Block Volume Management Plugin for
more information. When enabling the Block Volume Management plugin, ensure
that the instance is running version 1.23.0 or newer of the Oracle Cloud Agent software.
For paravirtualized attachments on virtual machine (VM) instances, optionally
encrypt data that is transferred between the instance and the Block Volume service storage servers by
selecting the Use in-transit encryption check box.
If you configured the volume to use an encryption key that you manage through the
Vault service, this key is used for
paravirtualized in-transit encryption. Otherwise, the Oracle-provided encryption
key is used. When you attach the volume to a bare metal instance that supports in-transit encryption, in-transit
encryption is enabled by default and is not configurable. For more information
about in-transit encryption, see Block Volume Encryption.
When the volume's state is Attached, if the attachment type is Paravirtualized, the
volume is connected automatically and you can use it. If the attachment type is
iSCSI, you need
to connect to the volume first. For more information, see Connecting to a Block Volume.
On Linux-based instances, if you want to automatically mount volumes when the
instance starts, you need to set some specific options in the
/etc/fstab file, or the instance might fail to start. This
applies to both iSCSI and paravirtualized attachment types. For volumes that use
consistent device paths, see fstab Options for Block Volumes Using Consistent Device Paths.
For all other volumes, see Traditional fstab Options.