Category: Aws

• Its network volume or Network volume like(Network Pendrive not physical drive) we can add to any EC2 instance as store space.
• It will not terminate after you terminate your EC2 instacne.
• You can attach 1 volume to 1 instance at a time and also need to be in same availability zone.
• Root EBS volume will be deleted not the others attached volume while the EC2 instance terminates

EBS Volume Snapshots

• Backup your EBS volume by taking a snpshots

AMI

Amazon Machine Images are a customization of an EC2 instance, that means we can customize a ec2 instacne then latter we can reuse that image. The main facility we will get from AMI is faster boot and configuration time because those things are already install in that AMI.

• AMI create for specific region

EBS Volume types

• GP2/GP3(SSD) : General purpose SSD volume that balance price and performance
• io1 / io2 Block Express (SSD) : Highest-performace SSD volumn for mission-critical low latancy or high-throughput(In same Availability zone io1/io2 volume can be use by multiple EC2 instance upto 16 instance)
• st1 (HDD): Low cost hdd volume
• sc1 (HDD) :Lowest cost HDD volume designed for less frequently access
• Only gp2,gp3,io1,io2 can be use as a boot volume
  
  Better check this https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volume-types.html

IOPS; I/O ops per sec

• Its a content Delivery Network(CDN).
• It Improves read performance, content is cached at the edge.
• 216 Point of Precesecne globally (edge locations).
• It DDos protection, integrations with Shield, AWS Web Application Firewall.
• Can Expose external HTTPS and can talk to internal HTTPS backends.

Cloud Front – Origins

• S3 Bucket
  • For distributing files and caching them at the edge.
  • Enhanced security with CloudFront Origin Access identity (OAI)
  • CloudFront can be used as an ingress (to upload files to S3)
• Custom Origin(HTTP)
  • It can be any HTTP end point like ALB(Applicatiion Load Balancer)
  • It can be EC2 instance(Ec2 instance must be public)
  • S3 static website.

AWS has many kind of S3 storage class

Amazon S3 Standard (S3 Standard)

1. Designed for high durability of 99.999999999% of objects across multiple Availability Zones.
2. If you store 10,000000 objects with Amazon S3, you can on average expect to incur a loss of a single object once every 10,000 years.
3. 99.99% Availability over a given year.
4. Sustain 2 concurrent facility failures.

Use case:
Big data analytics, mobile & gaming applications, content distribution…

Amazon S3 Standard-Infrequent Access (S3 Standard-IA)

1. Suitable for data that is less frequently accessed but requires rapid access when needed.
2. Designed for high durability of 99.999999999% of objects across multiple Availability Zones.
3. Low cost compared to Amazon s3 Standard
4. 99.99% Availability
5. Sustain 2 concurrent facility failures.

Use case:
As a data store for disaster recovery, backups…..

Amazon S3 One Zone-Infrequent Access (S3 One Zone-IA)

1. Same as AI but is stored in a single AZ.
2. High durability of 99.999999999% of the object in a single AZ. That means data loss when your AZ is destroyed.
3. 99.95% Availability.
4. Low latency and high throughput performance
5. Low cost compared to AI (by 20%)

Use case:
Storing secondary backup copies of on-remise data, or storing any kind of data so that we can recreate.

S3 Intelligent-Tiering

1. Low latency and high throughput performance as S3 Standard.
2. Small monthly monitoring and auto-tiering fee.
3. Automatically moves objects between two access tiers based on changing access patterns.
4. Designed for high durability of 99.999999999% of objects across multiple Availability Zones.
5. 99.99% Availability over a given year.

Amazon S3 Glacier

1. Low-cost object storage meant for archiving/ backup
2. Data is retained for the longer term(10s of year).
3. It’s a big alternative to on-premise magnetic tape storage.
4. The average annual durability is 99.999999%.
5. Cost per storage per month ($0.0041/GB) + retrieval cost.
6. Each item in Glacier is called “Archive” (up to 40TB).
7. Archives are stored in “Vaults”.

Use case:
Storing secondary backup copies of on-remise data, or storing any kind of data so that we can recreate.

Before Create S3 bucket replication we should consider some things which are mention below.

1. After enabling Replication only new objects are replicated not those which are previously created.
2. Delete operations are not replicated.
3. We cannot create chaining replication.

Don’t put your logging bucket to be monitored bucket. It will create a huge logging loop and your bucket will grow exponentially. End of the day it creates a big amount of Money.