Create and Attach EBS Volumes to Instances.

When working with Amazon Web Services (AWS), Elastic Block Store (EBS) volumes provide persistent block storage for your Amazon EC2 instances. This guide walks you through the process of creating and attaching EBS volumes to instances, with step-by-step configuration, scripting automation, and examples that address multiple scenarios.

Table of Contents

1. What is an EBS Volume?
2. Key Features of EBS
3. Steps to Create and Attach EBS Volumes
   • Using the AWS Management Console
   • Using the AWS CLI
4. Automating EBS Volume Attachment with Scripting
5. Example Scenarios
6. Best Practices for EBS Volumes
7. FAQs on EBS Volumes

1. What is an EBS Volume?

Amazon Elastic Block Store (EBS) is a high-performance block storage service designed for EC2 instances. It provides:

• Persistent storage: Data is retained even when instances are stopped.
• Low latency: Ensures optimal performance for applications.
• Flexibility: Tailored to meet specific storage requirements (SSD, HDD, etc.).

Common use cases for EBS volumes include hosting databases, file systems, or any workload requiring persistent storage.

2. Key Features of EBS

1. Types of EBS Volumes

• General Purpose SSD (gp3, gp2): Ideal for most workloads.
• Provisioned IOPS SSD (io2, io1): Optimized for high-performance databases.
• Throughput Optimized HDD (st1): For streaming workloads like big data.
• Cold HDD (sc1): Best for infrequent access.

2. Snapshots

EBS supports snapshots to back up data incrementally and restore volumes as needed.

3. Encryption

Data stored in EBS volumes can be encrypted using AWS-managed or customer-managed keys.

3. Steps to Create and Attach EBS Volumes to Instances.

Using the AWS Management Console

Step 1: Create an EBS Volume

1. Navigate to the EC2 Dashboard in the AWS Management Console.
2. Under the “Elastic Block Store” section, click on Volumes.
3. Click Create Volume.
4. Configure the volume:
   • Size: Specify the size in GiB (e.g., 20 GiB).
   • Volume Type: Choose from gp3, io1, st1, etc.
   • Availability Zone: Select the same zone as your EC2 instance.
5. Click Create Volume.

Step 2: Attach the Volume to an EC2 Instance

1. From the Volumes page, select the newly created volume.
2. Click Actions > Attach Volume.
3. Select the target EC2 instance from the list.
4. Specify a device name (e.g., /dev/xvdf) and click Attach.

Step 3: Configure the Instance to Use the Volume

1. SSH into the EC2 instance.
2. Use lsblk to verify the new volume is attached:

   lsblk
   

3. Create a file system on the volume:

   sudo mkfs.ext4 /dev/xvdf
   

4. Mount the volume:

   sudo mkdir /mnt/data
   sudo mount /dev/xvdf /mnt/data
   

5. Verify the setup:

   df -h
   

6. Add the volume to /etc/fstab for automatic mounting:

   echo '/dev/xvdf /mnt/data ext4 defaults,nofail 0 2' | sudo tee -a /etc/fstab
   

Using the AWS CLI

Step 1: Create an EBS Volume

Run the following command to create a volume:

aws ec2 create-volume \
  --availability-zone us-east-1a \
  --size 20 \
  --volume-type gp2

The output includes the Volume ID.

Step 2: Attach the Volume to an Instance

Use the Volume ID and Instance ID to attach the volume:

aws ec2 attach-volume \
  --volume-id vol-0abcd1234efgh5678 \
  --instance-id i-0abcd1234efgh5678 \
  --device /dev/xvdf

Step 3: Configure the Instance

Follow the same steps as in the console approach to create a file system, mount the volume, and update /etc/fstab.

4. Automating EBS Volume Attachment with Scripting

Automation ensures consistency and saves time in dynamic environments. Below is an example script using AWS CLI and Bash:

Bash Script to Create and Attach EBS Volumes

#!/bin/bash

# Variables
AVAILABILITY_ZONE="us-east-1a"
VOLUME_SIZE=20
INSTANCE_ID="i-0abcd1234efgh5678"
DEVICE_NAME="/dev/xvdf"

# Step 1: Create EBS Volume
VOLUME_ID=$(aws ec2 create-volume \
  --availability-zone $AVAILABILITY_ZONE \
  --size $VOLUME_SIZE \
  --volume-type gp2 \
  --query 'VolumeId' --output text)

echo "Created Volume: $VOLUME_ID"

# Step 2: Attach Volume to Instance
aws ec2 attach-volume \
  --volume-id $VOLUME_ID \
  --instance-id $INSTANCE_ID \
  --device $DEVICE_NAME

echo "Attached Volume $VOLUME_ID to Instance $INSTANCE_ID"

# Step 3: Configure the Instance
ssh -o StrictHostKeyChecking=no ec2-user@<INSTANCE_PUBLIC_IP> << EOF
  sudo mkfs.ext4 $DEVICE_NAME
  sudo mkdir -p /mnt/data
  sudo mount $DEVICE_NAME /mnt/data
  echo '$DEVICE_NAME /mnt/data ext4 defaults,nofail 0 2' | sudo tee -a /etc/fstab
EOF

echo "Volume configured and mounted on the instance."

5. Example Scenarios

Scenario 1: Expanding an Existing Volume

1. Stop the application using the volume.
2. Modify the volume size:

   aws ec2 modify-volume --volume-id vol-0abcd1234efgh5678 --size 50
   

3. Resize the file system:

   sudo resize2fs /dev/xvdf
   

Scenario 2: Detaching and Reattaching Volumes

1. Detach the volume:

   aws ec2 detach-volume --volume-id vol-0abcd1234efgh5678
   

2. Attach the volume to a different instance:

   aws ec2 attach-volume --volume-id vol-0abcd1234efgh5678 --instance-id i-1wxyz5678mnop9012 --device /dev/xvdf
   

6. Best Practices for EBS Volumes

• Choose the Right Volume Type: Match your workload’s performance and cost requirements.
• Regularly Back Up Data: Use snapshots to ensure data recovery.
• Enable Encryption: Protect sensitive data with AWS KMS.
• Monitor Performance: Use CloudWatch metrics to track IOPS, throughput, and latency.
• Optimize Costs: Delete unused volumes to avoid unnecessary charges.

7. FAQs on EBS Volumes

Q1: Can I attach an EBS volume to multiple instances?

A: Standard EBS volumes are limited to a single instance. For shared storage, use Amazon EFS or EBS Multi-Attach volumes.

Q2: What happens to the data when I terminate an instance?

A: By default, root volumes are deleted, while additional volumes persist. You can modify this behavior.

Q3: How do I migrate an EBS volume to a different region?

A: Create a snapshot, copy it to the target region, and create a new volume from the snapshot.

Conclusion

EBS volumes are a cornerstone of AWS’s block storage services. Whether you’re configuring volumes via the console, CLI, or automated scripts, understanding their features and best practices ensures optimal performance and cost-effectiveness. Following the steps outlined in this guide, you can confidently create, attach, and manage EBS volumes for any workload.

Learn More about: How to Create and Manage RDS Databases on AWS