EBS-Whitepaper

EBS:  (Elastic Block Store)

-Used for Create Partition/ File system, OS installation.

- Installation is possible on block storage.

-Whenever installation comes it has to be in EBS.
- Amazon EBS volumes cannot be shared between instances.
 -EBS Optimization is a network traffic optimization, it does not change the I/O speed of the volume. Istance store is cheaper and faster for performance.
 Instance Store Lifetime

Instance Store data
 - Persists only data in the instance store persis during the lifetime of its associated instance and  instance reboots. 

-Is lost when the instance stops/ terminates/ underlying disk drive fails.

Root primary/bootable disk

/dev/ssda1 :  Hypervisor Kernal is going to refer to

Snapshot contains image:

Magnetic  Old and slow ones

SSD : New generation/ performance guaranteed . Very high performance.

Provisioned  types: is the most suitable for performance

Provisioned IOPs:When Low latency and High throughput workload required. 4GB to 16 TiB volume supported

Throughput related to magnetic volume types

Name of hypervisor is : XEN which is based on Linux

When the server is storage, we are paying for the capacity (EBS). Because space is allocated for this,

All EBS comes from centralize storage system:

Actually the disk/EBS is lying on the central storage.

EBS volume: For any kind of installations.

Box : cpu+ mem+ IO+ disk /// + Local Disk

Local Disk:

Very fast accsss to local disk: Instance Store/Ephemeral Storage. Not persistent. I am goin to lose the data next time restart. They are local persisted disk. . Very high caching performance.

Instance Store added only during server creation.  Don’t use instance store when you have important data and want to preserve it.

We can take a back up of instance store.

Ebs using centralized storage, Ephemeral is using local storage

Snapshot is being created for each of the disk/storage we have in case of multiple volumes.
A snapshot is constrained to the AWS Region where it was created. 

For eg. Box D-drive--à Snapshot Snap-D

We can restore my drive from the snapshot.

Image contains references to multiple snapshot. If the Image is using the snapshots they cannot be deleted.

So first I need to delete the Image/AMI first. Then only I will be able to delete the snapshots. Essentially the actual data is sitting in the snapshot, so we are charged for the snapshot. For eg, how much space it is occupying etc.
 You can back up the data on your Amazon EBS volumes to Amazon S3 by taking point-in-time snapshots.

If you have database on D drive, we can take a snapshot of D drive.

AMI/Image:[snapshot1 + Snapshot2…]

When we create an AMI, there is an underlying snapshot that also get created. So if we deregister an ami, its snapshot should also be deleted  otherwise it will cost.

 Snapshots across Region : Making it possible to use multiple Regions for geographical expansion, data center migration, and disaster recovery.