0% found this document useful (0 votes)
5 views21 pages

AWS SOA Module04

The document provides an overview of storage systems in AWS, comparing block storage (Amazon EBS) and object storage (Amazon S3), highlighting their characteristics and use cases. It details Amazon EBS volume types, IOPS, snapshots, instance storage, and Amazon Elastic File System (EFS), as well as the organization and management of data in Amazon S3. Key features include data durability, versioning, and the unique requirements for bucket naming in S3.

Uploaded by

macolindres
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
5 views21 pages

AWS SOA Module04

The document provides an overview of storage systems in AWS, comparing block storage (Amazon EBS) and object storage (Amazon S3), highlighting their characteristics and use cases. It details Amazon EBS volume types, IOPS, snapshots, instance storage, and Amazon Elastic File System (EFS), as well as the organization and management of data in Amazon S3. Key features include data durability, versioning, and the unique requirements for bucket naming in S3.

Uploaded by

macolindres
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 21

STORAGE SYSTEMS IN AWS

SYSTEM OPERATIONS IN AWS - MODULE 4


Block Storage vs Object Storage

Block Storage Object Storage


 Mountable drive  100% API driven Amazon
Amazon EBS S3

 Unformatted drive space  Applications make calls to the object


 Provisioned and attached to EC2 storage services
instances  Granular control over content and
 Content management managed by OS more visibility of usage
of the instance to which the volumen is
attached.  Do not requiere pre-provisioning
AWS Storage Selection Criteria

 Block Storage vs Object Storage

 Retrieval Times (Hot vs Cold Storage)

 Cost Efficiency
Amazon Elastic Block Store

 Fundational block storage service


 Built as Network-attached
 Once created a volumen’s lifecycle is
fundamentally independent from the
EC2 instance
 Volumes cannot be mounted across AZs
Amazon EBS Volume Types
Amazon EBS IOPS

 EBS gp2 volumes have a set amount of IOPS: 3 IOPS/GB


 A 1 TB volumen has 3,000 IOPs
 Maximum IOPs for gp2 is 10,000
 There is a minimum of 100 IOPs provisioned on all gp2 volumes.
Amazon EC2 Capacity and IOPS/Throughput

 There is a limit in the amount of IOPS that can come out of an instance
 More volumes can provide more IOPS up to a limit
 Max throughput that some instances can Support is 12 GB/s
Mounting Amazon EBS Volumes

 Amazon EBS volumes operate independently from EC2 instances


 EC2 instance type can be changed
 EBS volumes persist when an instance is stopped
 Amazon EBS volumes can only attach to one Amazon EC2 instance at a time
 To mount an Amazon EBS volumen use the following command:
aws ec2 attach-volumen –volumen-id vol-1234567890abcdef0 \
--instance-id i-abc1234 –device /dev/sdf
Amazon EBS Snapshots
 Amazon EBS volumes live in only one AZ
 To improve data durability volume snapshots can be used
 Snapshots create permanente images of the volumen and store them at the regional
level.
 Snapshots are locked to the region where they were created.
 Snaptshots can be copied to a different region (it will have a new ID)
 To create a snapshot use the following command:
aws ec2 create-snapshot --volumen-id vol-0cb5b2dee8805e563 \
--description “My root volumen snapshot”
Instance Storage

 Available for some type of instances


 Ideal for temporary storage (buffers, caches, etc)
 Design for inexpensive, disposable, usually high-speed communication
 Storage is not persistent
 Only available at instance creation time (cannot be added later)
Amazon Elastic File System (Amazon EFS)

 Designed to provide regional, durable, multi-user file systems


 It is a fully managed file storage service
 Multiple Linux Amazon EC2 instances connect to Amazon EFS
 It can also be connected to on-premise Linux servers through AWS Direct Connect
Provisioning Amazon EFS
 To create an Amazon EFS from cli, use the following command:
aws efs create-file-system –creation-token MyEFS –region us-east-1
Amazon S3

 Amazon S3 is regionally provisioned object storage service.


 Content saved into Amazon S3 is automatically replicated into at least three facilities
 There is no data minimum or data limit
 Billing is applied to:
 Amount of storage for the time its in storage
 Charges for API calls in and out of the system
 Data transfered out of the region
Amazon S3 Buckets

 Content stored in Amazon S3 is organized in buckets.


 Bucket name must be unique across all AWS accounts
 Bucket name must adhere to the following rules:
 Name can be between 3 and 63 characters long
 Only lowercase characters, numbers, periods, and dashes.
 Must start with a lowercase letter or number
 Cannot contain underscores or end with a dash
Amazon S3 Storage Classes
Amazon S3 Storage Classes
Amazon S3 Versioning

 Use versioning to keep multiple


versions of an object in one bucket
 Enabling and suspending versioning is
done at the bucket level
 All objects added to a version enabled
bucket will have a unique version ID
Amazon S3 Versioning Delete Operation
Amazon S3 Versioning Delete Operation

 Original object cannot be retrieved


 An existing version of an object can be
retrieved specifying the ID with a GET
operation.
Amazon S3 Versioning Delete Operation

 An object can be by specifying the


version ID
 Only the owner of an Amazon S3
bucket can permanently delete a
version

You might also like