DAY 14 :📦 AWS Storage Types: Choosing the Right Fit for Your Needs
"I'm a 3rd-year Computer Engineering student at Marwadi University with skills in C++, web development (MERN stack), and DevOps tools like Kubernetes. I contribute to open-source projects and share tech knowledge on GitHub and LinkedIn. I'm learning cloud technologies and app deployment. As an Internshala Student Partner, I help others find jobs and courses." now currently focusing on #90DaysOfDevops
Storage in aws
Instance Store:
Temporary block-level storage.
Data is lost if the instance is stopped and started.
Block Storage (EBS):
Breaks data into blocks and presents them as a volume or hard drive.
Can be mounted and booted (OS installation possible).
Specific to an Availability Zone (AZ).
Servers in one AZ cannot attach an EBS volume from another AZ.
File Storage (EFS):
Stores data in a hierarchical structure of files and folders.
Accessible remotely by multiple machines simultaneously.
Cannot be used as a boot volume (OS installation not possible).
Object Storage (S3):
Stores objects (files) in a flat file structure without sub-directories.
Cannot be booted or mounted.
Suitable for static websites, media files, logs, traces, and audit reports.
Different storage classes affect accessibility, resiliency, and cost:
S3 Standard: Default and most expensive.
Standard-IA: Same reliability as S3 Standard but with a retrieval fee.
Glacier Instant: For rarely used files that need instant retrieval.
Glacier Flexible: Cheaper than Glacier Instant, but retrieval takes longer (5-12 hours for bulk, 3-5 hours for standard, 1-5 minutes for expedited).
Glacier Deep Archive: Cheapest option with the longest retrieval time.
This summary highlights the key features and limitations of each storage type, helping users choose the appropriate option based on their needs.
Thankyou for reading !!!!!!
