Skip to main content

Documentation Index

Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt

Use this file to discover all available pages before exploring further.

Welcome back to the second part of our EBS demo. In this lesson, you’ll learn how to transfer an EBS volume between servers—first within the same availability zone and then across different availability zones. Previously, we moved our EBS volume from Server One to Server Two seamlessly because both resided in the same availability zone. Since an EBS volume is zonal, it can be attached to any EC2 instance within its current zone. Now, we’ll move the EBS volume to Server Three, which is located in a different availability zone (us-east-1b).
Before moving volumes, always ensure that any active file systems are unmounted to avoid data corruption.

​
Unmounting the Volume

On the current server where the volume is in use, unmount it by executing: 
sudo umount /ebsdemo
After unmounting, verify that no file systems are mounted by listing block devices: 
lsblk
Expected output:
NAMEMAJ:MINRMSIZEROTYPEMOUNTPOINTS
xvda202:008G0disk
├─xvda1202:108G0part/
├─xvda2259:0000part
└─xvda128259:1010M0part
xvdf202:80010G0disk
Verify the file system type on the volume: 
sudo file -s /dev/xvdf
You should see output similar to: /dev/xvdf: SGI XFS filesystem data (blksz 4096, inosz 512, v2 dirs) Next, create a mount point and mount the volume to verify the data inside: 
sudo mkdir /ebsdemo
sudo mount /dev/xvdf /ebsdemo
cd /ebsdemo
ls
cat demo.txt
The file “demo.txt” should display: I made this on server Finally, unmount the volume again: 
cd ..
sudo umount /ebsdemo
Confirm that the volume is not mounted by checking: 
df -k

​
Detaching and Moving the Volume

With the volume unmounted, log into your AWS console and navigate to the EBS Volumes section. Select the volume, and ensure it is detached or in the process of detaching. Wait until its status changes to “available.” Refresh the page if necessary.
The image shows an AWS EC2 dashboard displaying a list of Elastic Block Store (EBS) volumes, with details about a selected volume named "demo-volume." Options for managing the volume are visible in a dropdown menu.
Next, click the “Attach volume” button to try attaching the volume to Server Three. Note that only servers in the same availability zone (Server One and Server Two) will appear in the instance selection dropdown.
The image shows an AWS EC2 interface for attaching a volume to an instance, with options to select an instance from a dropdown menu.

​
Creating a Snapshot to Overcome Availability Zone Limitations

Because you cannot directly attach an EBS volume to an instance in a different availability zone, the solution is to create a snapshot of your volume. Follow these steps:
  1. Select the volume.
  2. Choose “Actions” > “Create snapshot.”
  3. (Optional) Add a description (e.g., “my snapshot”) and confirm.
Creating a snapshot produces an exact copy of your volume’s data.
The image shows an AWS interface for creating a snapshot of an Amazon EBS volume, with fields for volume ID, description, encryption, and tags. A button labeled "Create snapshot" is highlighted.
Monitor the snapshot’s progress in the Snapshots section. It may initially show a status like “pending” or a progress percentage until it turns “available.”
The image shows an AWS EC2 console displaying a list of EBS snapshots with details such as snapshot ID, volume size, description, storage tier, and status. One snapshot is pending, while others are completed.

​
Creating a New Volume in a Different Availability Zone

Once the snapshot is available, follow these steps to create a new volume in the target availability zone:
  1. Select the snapshot.
  2. From the “Actions” dropdown, choose “Create volume from snapshot.”
  3. Change the availability zone to the target zone (e.g., US East 1B for Server Three). You can adjust volume type, size, and other settings as needed.
  4. (Optional) Add tags (for example, name the volume “EBS clone”).
The image shows a screenshot of AWS volume settings, including options for volume type, size, IOPS, throughput, availability zone, and encryption.
After creating the new volume, confirm in the Volumes section that the clone appears in the correct availability zone.
The image shows an AWS EC2 dashboard displaying a list of volumes with details such as throughput, snapshot, creation date, availability zone, volume state, alarm status, and attached instances. The sidebar includes navigation options for various EC2 and Elastic Block Store features.
Now, attach the new volume to Server Three:
The image shows an AWS EC2 interface for attaching a volume to an instance, with options to select the instance and device name. There is a button to "Attach volume" at the bottom.

​
Verifying on Server Three

Log into Server Three via your terminal and run the following commands to verify that the block device is attached and to confirm the file system: 
lsblk
Expected output should look similar to this:
NAMEMAJ:MINRMSIZEROTYPEMOUNTPOINTS
xvda202:008G0disk
├─xvda1202:108G0part/
├─xvda127259:001M0part
└─xvda128259:1010M0part
xvdf202:80010G0disk
Check the filesystem on the new volume: 
sudo file -s /dev/xvdf
Expected output: /dev/xvdf: SGI XFS filesystem data (blksz 4096, inosz 512, v2 dirs) Then, create the mount point and mount the volume: 
sudo mkdir /ebsdemo
sudo mount /dev/xvdf /ebsdemo
Change directory to the mount point and verify the transferred data: 
cd /ebsdemo/
ls
cat demo.txt
The file “demo.txt” should display: I made this on server This confirms that the original volume’s data has been successfully cloned and attached to Server Three in a different availability zone.

​
Moving Volumes Across Regions

If you need to migrate the volume to a completely different AWS region (for example, from Northern Virginia to Ohio), you cannot directly create a volume from a snapshot in another region. Instead, you must:
  1. Copy the snapshot from the original region to the desired region.
  2. Create a volume from the copied snapshot in the target region.
To copy the snapshot:
  1. Select the snapshot.
  2. Click “Actions” and select “Copy snapshot.”
  3. Provide a description such as “copy of my snapshot.”
  4. Specify the destination region (e.g., US East 2 for Ohio).
The image shows an AWS interface for copying a snapshot, with fields for snapshot ID, description, destination region, and encryption options.
Once the snapshot copy is complete, switch to the target region (e.g., us-east-2), locate the snapshot in the Snapshots section, and then click “Create volume from snapshot.” Choose the correct availability zone (e.g., us-east-2a) for your EC2 instance. After creation, the new volume will be available.
The image shows an AWS EC2 dashboard displaying a list of two EBS volumes with details such as volume ID, type, size, IOPS, and availability zone.
Finally, attach the newly created volume to your target EC2 instance:
The image shows an AWS EC2 interface for attaching a volume to an instance, with options to select the instance and availability zone.
This completes the process of migrating an EBS volume across different availability zones and regions. Happy configuring!

Watch Video

Practice Lab