Everything that the AWS storage devices can do! — Day 2

Storage Devices that available

1. Simple Storage Service (S3):
2. Glacier
3. Elastic Block Store
4. Elastic File System
5. Storage Gateway
6. Snowball.

Simple Storage Service : ?

1. Designed to store and access any kind of data over internet.
2. Server-less Service
3. Yes! Obviously file server ,an operating system, a hard disk but we don’t need to be concerned about that at all. We just simply need to create this thing called a bucket and then we upload objects to that bucket.
4. Bucket grows as we add objects to it and the size of bucket is theoretically unlimited.

Glacier :?

1. Mainly used for long term archiving data.
2. Server-less Service
3. Same like S3 but it not as readily accessible.(so it should only be used for content that is to be archived).

we can also set up automatically migrate old date to glacier from s3 forlong term archiving data.

Elastic Block Store (EBS):?

1. low latency block storage and it’s specifically for attaching to servers that are launched with the Amazon ec2 service.(similar to attaching hard drive to our computer)

Elastic File System (EFS):?

Network attached storage and it’s specifically for Amazon EC2 servers. Because it is network attached store, this allows multiple servers to access one data source in a similar way to Network access storage(NAS) on your network at home can be accessed by multiple computers on that network.

AWS Storage Gateway :?

Enables hybrid storage between on-premise environments and the AWS cloud. It provides a low latency performance by caching frequently used data on-premises while storing the less frequently data in Amazon Cloud storage services.

Snow Ball :?

1. Device is portable, Petabyte scalable ,Data Storage device that can be used to migrate data and large amount data from on-premise environments over the AWS cloud.
2. Simply download data to Snowball device and send it off to AWS who will then upload that data to an AWS storage services.

…. Now we can create a VPC inside (VPC — own private space within AWS cloud and that is an impenetrable fortress against attack and no one will enter to own private space without until allowing that to happen.)

Now , just say we launched two servers in our VPC now we want these servers to have data and to access data (in normal environment we add hard drive to that server , so in the same way we can attach an AWS EBS storage device to server).

Now , that data to be available to both of those servers? So here we’ve only got two volumes , what if we want to have only one volume data that to available both servers? — (Purchase a NAS network attached storage device. You would attach it to your network you would set up your operating system) — Same way we can do in Amazon — elastic file system is network attached storage and so that with a mount target can enable multiple servers.

Now what if we don’t want to worry about mount targets and block devices and all this sort of stuff? We just want somewhere we can upload objects to in a similar way do we do with Google Drive or something like that and we also want to have an automated solution that over time migrates that data over to something more low cost and more long term for archiving now — That is where Amazon S3 comes in and so we can use Amazon s3 to create a bucket.

Amazon S3 : ?

1. Create a Bucket (unique name).
2. Store objects to that bucket, delete objects do what ever we need.(simple key value store)
3. And also we can set up a life cycle rule on that bucket so that over a period time as object age , they can be migrated to Glacier Vault for long term archiving.
4. But the advantages of s3 will be located in the AWS cloud not in VPC (our private space) — were vpc endpoint comes in.

5. Unique namespace (name will be unique globally) — bucket contain DNS address and bucket must contain unique name to generate unique DNS address.

Ex of S3 URL : https://ap-south-1.amazonaws.com/everythingatonce

Advantages of S3 Buckets ?

1. Buckets (Unique Name)
2. Storing data in buckets — Each object can be stored and retrieved by using a unique developer assigned-key — Each object can contain upto 5 TB of data.
3. Download data — at any time where you want.
4. Permissions — also grant or deny access to others who want to access S3 Bucket.
5. Standard Interfaces : SOAP/Rest can work with any development tool kit.
6. Security : By Protecting unauthorized users from accessing data.

Why S3 is simple key value store ?

1. Key — name of the object .For example, Availability.xml, airport.xlsx, etc. You can use the key to retrieve the object.
2. Value — Data which made up of sequence of bytes.
3. Version ID — Unique identifies the object (generated by s3 when we upload to s3 bucket).
4. Metadata: Meta info about data that we are storing.
5. Sub resources: mechanism is used to store object-specific information.
6. Access Control Information: we can put the permissions individually on objects we added in bucket.

S3 Concepts:

• Buckets — (container for storing the objects)
• Objects -(entities which are stored in an S3 bucket)
• Keys (object in a bucket is associated with one key — unique identifier for an object)
• Regions — geographical region in which you want to store the buckets that you have created ,latency, minimize costs or address regulatory requirements.
• Data Consistency Model (2 types)

a. Read-after-write consistency for PUTS of new objects. (Across multiple servers to achieve high availability for immediately available to read the object) — never take time to update.(list keys immediately within bucket)

b.Eventual consistency for overwrite PUTS and DELETES (the changes are reflected eventually, and they are not available immediately.Until the change is fully propagated, the S3 might return the list of the deleted key or data).

Yes!, we have know about little in S3 bucket let see another part how to create S3 Buckets.

In case of queries please feel free to comment!.

Thanks for the time.