Skip to main content
Copy EBS Volume Actions
Matt Houser avatar
Written by Matt Houser
Updated over 6 years ago

Description

The Copy EBS Volume action is used to copy an existing volume and optionally attach it to an EC2 instance.

Important Note

Unmount any existing devices before detaching an existing volume. Failure to do so may result in the volume being stuck in a "busy" state.

Settings

Please see Common Action Settings for a description of settings common to all action types.

Volume ID

Indicate the volume id of your EBS volume to copy. This value usually looks like "vol-84a3dc7b". This volume must reside in the region specified.

Consistency Method

Indicate the method in which to ensure volume consistency. Currently, two options exist:

  • None - do nothing

  • Stop Instance - Stop and restart the instance

Attach New Volume

Indicate the whether the new volume should be attached to an EC2 instance.

Target Instance ID

Indicate the instance ID of the target EC2 instance on which the volume is to be attached. This value usually looks like "i-84a3dc7b". This instance must reside in the region specified.

Device Name

Indicates the name of the device to attach the new volume as. This value usually looks like "/dev/sda1".

Stop Instance

Indicate whether the target EC2 instance should be automatically stopped and restarted during the attach process.

Detach Existing Device

Indicate whether any existing device should be detached before attaching the new device. If off, ensure that no device is attached before the action is executed otherwise the action will fail to attach the new drive.

Amazon Commands Used

The following Amazon AWS commands are used. The access key should have permission to execute all of them.

  • ec2:AssociateAddress

  • ec2:AttachVolume

  • ec2:CreateSnapshot

  • ec2:CreateTags

  • ec2:CreateVolume

  • ec2:DeleteSnapshot

  • ec2:DescribeAddresses

  • ec2:DescribeInstances

  • ec2:DescribeSnapshots

  • ec2:DescribeTags

  • ec2:DescribeVolumes

  • ec2:DetachVolume

  • ec2:StartInstances

  • ec2:StopInstances

Did this answer your question?