P. Poojaswini and D.

Nagaraju, International Journal of Research in Engineering, IT and Social Sciences, ISSN 2250-
0588, Impact Factor: 6.565, Volume 14 Issue 06, June 2024, Page 763-771

Operations on EBS Storage Service in AWS

1
P. Poojaswini 2Dr.D.Nagaraju
1
TE CSE, NEC, Gudur
2 Professor,CSE Department, NEC, Gudur

Abstract: EBS provides persistent storage volumes that can be dynamically attached to EC2 instances,
offering a range of operations critical to managing cloud-based workloads effectively. Elastic Block
Store (EBS) attachment and detachment are fundamental operations in cloud computing, particularly in
Amazon Web Services (AWS). EBS provides block-level storage volumes for EC2 instances, offering
persistence and flexibility. Attachment involves associating an EBS volume with an EC2 instance,
enabling it to access the data stored on the volume. Detachment, on the other hand, disconnects the
volume from the instance, allowing it to be reattached to another instance or remain unattached for
storage management purposes. These operations are crucial for dynamic scalability, data management,
and ensuring high availability in cloud environments.
Keywords: AWS, EC2 Instance, EBS Volumes, snapshots

I. INTRODUCTION

Amazon Elastic Block Store (EBS) is a foundational component of Amazon Web Services (AWS), providing
persistent block storage volumes that can be used with Amazon Elastic Compute Cloud (EC2) instances. Designed
for applications that require reliable and high-performance storage, EBS supports a wide range of workloads, from
small-scale test environments to large-scale enterprise applications. Effective management and optimization of
EBS volumes are crucial for maintaining application performance, ensuring data durability, and controlling costs.

Creating Volumes: Users can create EBS volumes of varying sizes and types, tailored to specific performance
needs and use cases. AWS offers different volume types, such as General Purpose SSD (gp2 and gp3), Provisioned
IOPS SSD (io1 and io2), Throughput Optimized HDD (st1), and Cold HDD (sc1).

Attaching and Detaching Volumes: EBS volumes can be attached to and detached from EC2 instances
dynamically, allowing flexible resource management.

Creating Snapshots : Snapshots provide a point-in-time backup of EBS volumes, essential for data protection and
recovery. These snapshots can be used to create new volumes or restore existing ones.

This paper explores various operations on EBS, focusing on creation, configuration, and management of EBS
volumes. Key operations include volume provisioning, snapshot management, performance tuning, and data
backup and recovery. The ability to create snapshots allows for data backup and versioning, enabling robust disaster
recovery solutions. Performance optimization is achieved through volume type selection (such as SSD and HDD
options), IOPS (Input/ Output Operations Per Second) tuning, and throughput adjustments.

Advanced operations like encryption and volume cloning further enhance security and operational efficiency.
EBS volumes can be encrypted to protect data at rest, ensuring compliance with security standards. Volume cloning
supports rapid environment replication and testing, aiding in DevOps practices. weather and news updates were
visible through the front of the glass while reflecting the user’s image on the mirror.

http://indusedu.org Page 763

This work is licensed under a Creative Commons Attribution 4.0 International License
P. Poojaswini and D. Nagaraju, International Journal of Research in Engineering, IT and Social Sciences, ISSN 2250-
0588, Impact Factor: 6.565, Volume 14 Issue 06, June 2024, Page 763-771

Attaching and detaching EBS volumes provide AWS users with the flexibility to manage their storage
resources efficiently. This capability supports dynamic workloads, ensures data persistence, and integrates
seamlessly with other AWS services. By following best practices for managing EBS volumes, organizations can
achieve high performance, reliability, and cost-effectiveness in their cloud storage solutions. Whether for scaling
applications, ensuring data durability, or optimizing costs, EBS attachment and detachment play a crucial role in
modern cloud infrastructure management.EBS (Elastic Block Store) attachment and detachment is ensuring data
integrity and proper resource management.

Fig1.Elastic Block Store

II.Implementation
Following are the steps followed to implement load balancing and auto scaling.
1. Launch an EC2 instance
2. Create an EBS volume
3. Attach volume to EBS
4. Connect an instance to RDP client
5. Configure secutity groups
6. De -attach volume from EBS
7. Create snapshot
8. Increasing volume size in win VM
9. Increasing volume size in Linux VM

Launch an EC2 Instance

Amazon Elastic Compute Cloud (EC2) is a web service that provides resizable compute capacity in the cloud. To
launch an EC2 instance (i.e., a virtual server), follow these steps:

• Navigate to the EC2 dashboard within the AWS Management Console.

• Click on the "Launch Instance" button to begin the instance creation process.
• Choose an Amazon Machine Image (AMI), which is a pre-configured template for your server. You can
select from a variety of operating systems and software configurations.
• Select an instance type based on your resource requirements.
• Configure instance details such as the number of instances, network settings, and storage options.
• Optionally, add tags to your instance for easier management and organization.
• Configure security groups to control inbound and outbound traffic to your instance. Define rules for protocols,
ports, and IP ranges.

http://indusedu.org Page 764

This work is licensed under a Creative Commons Attribution 4.0 International License
P. Poojaswini and D. Nagaraju, International Journal of Research in Engineering, IT and Social Sciences, ISSN 2250-
0588, Impact Factor: 6.565, Volume 14 Issue 06, June 2024, Page 763-771

Access Your Server:

Once your EC2 instance is running, you can access it using SSH (Secure Shell) for Linux instances or RDP
(Remote Desktop Protocol) for Windows instances. Use the key pair you created during instance launch to
authenticate the SSH or RDP session.

Fig 2. Launch an instance

Attaching an EBS Volume to an EC2 instance:

Attaching an EBS volume to an EC2 instance involves a series of steps to ensure the volume is properly connected
and ready for use. First, you need to navigate to the AWS Management Console and log in to your account. From the
home page, select the "EC2" service, which will take you to the EC2 Dashboard. In the dashboard, look for the "Elastic
Block Store" section in the left-hand menu and click on "Volumes." This page displays all your existing EBS volumes.
Identify the volume you want to attach to your EC2 instance.
Next, select the desired volume by checking the box next to it. With the volume selected, click on the "Actions"
dropdown menu at the top of the page and choose "Attach
Volume." This will open the "Attach Volume" dialog box. In this dialog, you need to specify the instance ID of the
EC2 instance to which you want to attach the volume. You can find the instance ID by navigating back to the EC2
Dashboard and selecting "Instances".

Fig 2.1: Attach an EBS volume

After entering the instance ID in the "Attach Volume" dialog, you will also need to specify the device name.
The device name follows a specific naming convention, typically something like /dev/sdf or /dev/ xvdf.

http://indusedu.org Page 765

This work is licensed under a Creative Commons Attribution 4.0 International License
P. Poojaswini and D. Nagaraju, International Journal of Research in Engineering, IT and Social Sciences, ISSN 2250-
0588, Impact Factor: 6.565, Volume 14 Issue 06, June 2024, Page 763-771

Connect an Instance to RDP Client:

Connecting an EC2 instance to an RDP (Remote Desktop Protocol) client allows you to manage and interact
with the instance's graphical user interface. To begin, ensure that your EC2 instance is running a Windows operating
system, as RDP is typically used for Windows- based instances. From the AWS Management Console, navigate to the
"EC2" service and select "Instances" from the left-hand menu. Locate the Windows instance you want to connect to
and verify that its status is "running."Next, ensure that the instance's security group has a rule that allows inbound
RDP traffic. In the "Description" tab of your instance, find the security group and click on its ID to open the security
group settings.
Now, open the downloaded .rdp file. This action should launch your default RDP client. If prompted with a security
warning, click "Connect" to proceed. In the RDP client window, enter the administrator username, which is typically
"Administrator," and paste the copied password. Click "OK" to log in.

Retrieve the Public IP or DNS Name:

• Go to the EC2 Dashboard.
• Select your running instance and find the Public IP or Public DNS under the instance details.
Download RDP File:
• From the EC2 Dashboard, with the instance selected, click on "Connect".
• Download the RDP connection file provided.
Connect Using an RDP Client:
• Open your RDP client (Remote Desktop Connection on Windows or any other RDP client for Mac/Linux).
• Use the downloaded RDP file or manually enter the Public IP or DNS of your instance.
Authenticate:
• When prompted, enter the username (usually Administrator for Windows Server instances).
• Retrieve the password from the EC2 console (Actions > Get Windows Password), using the private key file
(.pem) you downloaded earlier.

Fig 2.2 Connect an instance to RDP client

http://indusedu.org Page 766

This work is licensed under a Creative Commons Attribution 4.0 International License
P. Poojaswini and D. Nagaraju, International Journal of Research in Engineering, IT and Social Sciences, ISSN 2250-
0588, Impact Factor: 6.565, Volume 14 Issue 06, June 2024, Page 763-771

III. Configure Security Groups

• Select an existing security group or create a new one to control inbound traffic to your load balancer.
• Configure Routing
• Target group: Create a new target group or select an existing one.
• Target type: Choose between "Instances", "IP addresses", or "Lambda function".
• Name: Provide a name for the target group.
• Protocol: Select the protocol for routing traffic to targets (HTTP or HTTPS).
• Port: Specify the port on which targets receive traffic.
• Health checks: Configure health check settings (protocol, path, port, success codes, interval, timeout, and
thresholds)

Fig 3: Configure security Groups

Detach an EBS Volume:

Detaching an EBS volume from an EC2 instance involves a series of straightforward steps to ensure the
volume is properly disconnected and can be safely managed or reattached later. First, navigate to the AWS
Management Console and log in to your account. Once logged in, select the "EC2" service from the AWS
Management Console home page, which will take you to the EC2 Dashboard.
From the EC2 Dashboard, look for the "Elastic Block Store" section in the left-hand menu and click on
"Volumes." This page displays all your existing EBS volumes. Locate the volume you want to detach by checking
its status and identifying the volume ID. To detach the volume, ensure that the volume is currently attached to an
instance by checking the "Attachment Information" column.
Before detaching the volume, it’s important to ensure that the instance is not actively using it. Log in to the
EC2 instance via SSH (for Linux) or RDP (for Windows) and unmount the volume. On a Linux instance, you can
unmount the volume using a command like sudo umount /mnt’ if the volume is mounted to the /mnt' directory.

Create EBS Snapshot in AWS:

http://indusedu.org Page 767

This work is licensed under a Creative Commons Attribution 4.0 International License
P. Poojaswini and D. Nagaraju, International Journal of Research in Engineering, IT and Social Sciences, ISSN 2250-
0588, Impact Factor: 6.565, Volume 14 Issue 06, June 2024, Page 763-771

Creating a snapshot in Amazon Elastic Block Store (EBS) is a straightforward process that involves a few
key steps. To start, navigate to the Amazon EC2 dashboard within the AWS Management Console. From there,
select the "Snapshots" option under the "Elastic Block Store" section. Click on the "Create Snapshot" button to
initiate the process. You'll be prompted to choose the volume from which you want to create a snapshot. After
selecting the desired EBS volume, you can add a description to help identify the snapshot later.

• With the volume selected, click on the "Actions" button at the top of the page.
• From the dropdown menu, select "Create Snapshot".
• A dialog box will appear prompting you to enter details for the snapshot.
• Description: Enter a description for the snapshot to help you identify it later.
• Click "Add Tag" to add any tags for better management and organization. For example, you might add Name
tag.
• After entering the required details, click the "Create Snapshot" button.

Fig 3.1 Create Snapshot

Increasing volume size in WINVM:

Increasing the size of an EBS volume attached to a Windows EC2 instance involves a few steps that ensure
the volume is expanded and the additional space is made available to the Windows operating system. First, navigate
to the AWS Management Console and log in to your account. From the home page, select the "EC2" service to go
to the EC2 Dashboard.
Identify the volume you want to resize by checking its volume ID and current size. Select the volume by
clicking the checkbox next to it. Click on the "Actions" dropdown menu and choose "Modify Volume." In the
"Modify Volume" dialog, you can increase the size of the volume by entering the new desired size in the "Size
(GiB)" field. Ensure that the new size is larger than the current size. After specifying the new size, click the
"Modify" button. AWS will begin the process of resizing the volume, which typically takes a few minutes. You
can monitor the progress in the "State" column on the "Volumes" page.
• Login on AWS cloud console.
• Click on Services > Compute > EC2 > EC2 Dashboard.
• On the EC2 dashboard, click on Instance.
• Select the instance.

Increasing volume size in Linux VM:

http://indusedu.org Page 768

This work is licensed under a Creative Commons Attribution 4.0 International License
P. Poojaswini and D. Nagaraju, International Journal of Research in Engineering, IT and Social Sciences, ISSN 2250-
0588, Impact Factor: 6.565, Volume 14 Issue 06, June 2024, Page 763-771

Increasing the size of an EBS volume attached to a Linux EC2 instance involves several steps to ensure the
volume is resized and the additional space is available to the operating system. First, navigate to the AWS
Management Console and log in to your account. From the home page, select the "EC2" service to go to the EC2
Dashboard. In the left-hand menu, click on "Volumes" under the "Elastic Block Store" section to view a list of all
your EBS volumes.
Identify the volume you want to resize by checking its volume ID and current size. Select the volume by
clicking the checkbox next to it. Click on the "Actions" dropdown menu and choose "Modify Volume." In the
"Modify Volume" dialog, increase the size of the volume by entering the new desired size in the "Size (GiB)"
field. Ensure that the new size is larger than the current size. After specifying the new size, click the "Modify"
button. AWS will begin the process of resizing the volume, which typically takes a few minutes. You can monitor
the progress in the "State" column on the "Volumes" page.
• Locate the instance in your EC2 dashboard and click on the Instance ID.
• Click on the Storage tab and then on the Volume ID.
• In the Actions dropdown at the top of the page, click Modify Volume.
• Set the new size and save.

Once the volume modification is complete, the next step is to expand the filesystem on your Linux EC2
instance to utilize the new space. Connect to your Linux instance via SSH using terminal. After logging in, use the
command to list the block devices and verify that the operating system recognizes the increased size of the volume.
To resize the filesystem, you need to determine the filesystem type. For example, if your filesystem is ext4,
you can use the resize2fs command. First, check the filesystem type with df -T /dev/xvdf (replace /dev/xvdf with
your actual device name). Assuming it's ext4, unmount the volume if it is currently mounted using sudo umount
/dev/xvdf. Then, run sudo resize2fs /dev/xvdf to resize the filesystem. If the volume is not unmounted, you can
still resize it online without unmounting using sudo resize2fs /dev/xvdf.

IV. RESULTS

http://indusedu.org Page 769

This work is licensed under a Creative Commons Attribution 4.0 International License
P. Poojaswini and D. Nagaraju, International Journal of Research in Engineering, IT and Social Sciences, ISSN 2250-
0588, Impact Factor: 6.565, Volume 14 Issue 06, June 2024, Page 763-771

When you attach an EBS volume to an EC2 instance, the EC2 control plane allocates the necessary resources
for the volume to interact with the instance. For virtualized instances, an NVM virtual function is used, while for
bare metal instances, a physical function is utilized. The EBS control plane provides information to connect to the
EBS servers that store the encrypted volume data. This involves decrypting the volume's data key via AWS Key
Management Service (KMS) and securely transmitting it to the EC2 instance through the Nitro system. Once
attached, the instance can interact with the EBS volume as a block device. Detaching an EBS volume typically
requires the volume to be unmounted from the operating system to ensure no data corruption. However, in
situations where the volume does not detach cleanly, AWS provides a forced detach option. This can be useful
when an instance fails to release the volume due to ongoing processes. Forced detach can result in potential data
loss if there are pending write operations, so it should be used cautiously. This functionality has been integrated
into the AWS Management Console, offering a more user- friendly way to manage volume detachment compared
to using the command line or API.
EBS (Elastic Block Store) is a widely used storage service within the AWS cloud. It provides persistent block
storage volumes that act like virtual hard drives for your EC2 instances. These volumes are independent of the EC2
instance lifecycle, meaning your data remains secure even if you terminate the instance. EBS offers high scalability by
allowing you to easily attach more volumes for additional storage as needed.

V. Conclusion
Attaching and detaching EBS volumes provide AWS users with the flexibility to manage their storage resources
efficiently. This capability supports dynamic workloads, ensures data persistence, and integrates seamlessly with other
AWS services. By following best practices for managing EBS volumes, organizations can achieve high performance,
reliability, and cost-effectiveness in their cloud storage solutions. Whether for scaling applications, ensuring data
durability, or optimizing costs, EBS attachment and detachment play a crucial role in modern cloud infrastructure
management.EBS (Elastic Block Store) attachment and detachment is ensuring data integrity and proper resource
management. When attaching an EBS volume to an EC2 instance, ensure the volume is properly mounted and
accessible. During detachment, make sure any data is safely flushed and unmounted before detaching to avoid data
loss or corruption. Properly managing EBS volumes helps maintain a reliable and efficient AWS infrastructure. The
future of EBS in AWS is exciting, with a focus on enhanced performance, scalability, and integration. We can expect
breakthroughs in storage technology offering lower latency and higher IOPS for demanding applications. Scaling
massive EBS deployments might be simplified through features like automated scaling based on workload. AI
integration could introduce intelligent functionalities like self-optimizing configurations and tailored volume
recommendations. Look out for tighter bonds between EBS and other AWS services, potentially allowing on-demand
storage attached to serverless functions. As hybrid and multi-cloud environments become more commonplace, EBS
might evolve to seamlessly manage data mobility across various platforms. Security will unquestionably remain a
priority, with potential advancements in encryption and access controls to safeguard EBS volumes in complex cloud
deployments.

http://indusedu.org Page 770

This work is licensed under a Creative Commons Attribution 4.0 International License
P. Poojaswini and D. Nagaraju, International Journal of Research in Engineering, IT and Social Sciences, ISSN 2250-
0588, Impact Factor: 6.565, Volume 14 Issue 06, June 2024, Page 763-771

V1. REFERENCES
[1] Danielo Gonc¸alves Gomes and Jos´e Neuman de Souza, “An Autonomic Computing-based Architecture for
Cloud Computing Elasticity ,” Virtual University Institute (UFC VIRTUAL) , Fortaleza - Brazil .IEEE,2015
[2] Satish Narayana Srirama, Alireza Ostovar, “Optimal Resource Provisioning for Scaling Enterprise Ap
plications on the Cloud,” Institute of Computer Science,University of Tartu, Estonia.IEEE,2015
[3] Shridhar G.Domanal and G. Ram Mohana Reddy, “Load Balancing in Cloud Environment using a Novel
Hybrid Scheduling Algorithm ,”National Institute of Technology Karnataka, India.IEEE,2015 Surathkal,
Mangalore
[4] Ying Liu, Navaneeth Rameshan, Enric Monte, Vladimir Vlassov and Leandro Navarro, “ProRenaTa: Proactive
and Reactive Tuning to Scale a Distributed Storage System,” KTH Royal Institute of Technology,
Sweden.IEEE,2015
[5] Ali Yadavar Nikravesh, Samuel A. Ajila, Chung- Horng Lung, “Towards an Autonomic AutoScaling
Prediction System for Cloud Resource Provisioning,” Department of Systems andComputer Engineering,
Carleton University 1125 Colonel By Drive, Ottawa K1S 5B6, Ontario Canada.IEEE,2015
[6] Sidra Aslam, Maunam Ali Shah, “Load Balancing in Cloud Computing: A Survey of Modern
Techniques,”COMSATS Institute of information technology, Islamabad, Pakistan .IEEE,2015
[7] Mayanka Katyal, Atul Mishra, “A Comparative Study of Load Balancing in Cloud Computing Environment,”
YMCA University of Science and Technolohy ,Faridabad, Hariyana.India
[8] Sandeep Sharma, Sarabjit Singh, and Meenakshi Sharma, “Performance Analysis of Load Balancing
Algorithms,” World Academy of Science, Engineering and Technology.IEEE,2008
[9] A. Y. Nikravesh, S. A. Ajila, C.H. Lung, “Cloud resource autoscaling system based on Hidden Markov Model
(HMM)”,Proc. of the 8th IEEE International Conference on June 2014. Semantic Computing
[10] T. Lorido-Botran, J. Miguel-Alonso, J. A. Lozano, “A review of auto-scaling techniques for elastic
applications in cloud environments,” Journal of Grid Computing, vol. 12, no. 4, December 2014
[11] Resma K. S, Dr. Sharvani G. S, Edge Distributed Cloud Middleboxes International Journal Of Advance
Research, Ideas And Innovations In Technology, ISSN: 2454-132X, Volume 5, Issue 3. Luo, J., Rao, L., & Liu,
X. (2017). Spatio-Temporal Load Balancing For Energy Cost Optimization In Distributed Internet Data Centres.
IEEE Transactions On Cloud Computing, 3(3), 387– 397.

http://indusedu.org Page 771

This work is licensed under a Creative Commons Attribution 4.0 International License