added ec2 storage or ebs for aws ccp

Author: siv-the-programmer

Study_Notes/04_Ec2_STORAGE_EBS/01-ebs-overview.md

@@ -0,0 +1,51 @@
+Amazon Elastic Block Store (EBS) is persistent block-level storage designed to be used with Amazon EC2 instances.
+Block storage means the data is stored in fixed-size chunks (blocks), similar to a traditional hard drive or SSD.
+
+# EBS is primarily used for:
+
+Operating system disks
+
+Databases
+
+Application data requiring low latency
+
+Stateful workloads
+
+# Core properties:
+
+EBS volumes are attached to EC2 instances
+
+Each volume exists in one Availability Zone
+
+Data persists independently of the EC2 instance lifecycle
+
+Volumes can be detached and reattached to other instances in the same AZ
+
+EBS vs other storage:
+
+EBS ≠ S3 (object storage)
+
+EBS ≠ EFS (shared file storage)
+
+EBS behaves like a disk, not a bucket or shared folder
+
+# Volume types and intent:
+
+General Purpose SSD (gp3/gp2): default, balanced cost and performance
+
+Provisioned IOPS SSD (io2): mission-critical, predictable I/O
+
+Throughput Optimized HDD (st1): large sequential workloads
+
+Cold HDD (sc1): infrequently accessed data
+
+High-level design rule:
+If an EC2 instance needs a disk that survives stop/start, EBS is the default answer.
+
+# Exam traps:
+
+EBS is not regional
+
+EBS cannot be shared by default
+
+EBS is not free (storage + IOPS)

Study_Notes/04_Ec2_STORAGE_EBS/02-ebs-multi-attach.md

@@ -0,0 +1,42 @@
+EBS Multi-Attach allows a single EBS volume to be attached to multiple EC2 instances simultaneously.
+
+This feature exists to support clustered applications that require shared block storage.
+
+# Strict limitations:
+
+Only supported on io1 and io2 volumes
+
+All attached instances must be in the same Availability Zone
+
+Applications must coordinate writes (AWS does not handle locking)
+
+What Multi-Attach does NOT do:
+
+It does not provide file-level locking
+
+It does not prevent corruption
+
+It does not behave like EFS
+
+# Correct use cases:
+
+Databases with cluster-aware file systems
+
+Enterprise applications designed for shared block devices
+
+Incorrect use cases:
+
+General file sharing
+
+Web servers sharing assets
+
+Applications without write coordination
+
+# Exam logic:
+If AWS mentions “multiple EC2 instances access the same storage”:
+
+File-level → EFS
+
+Object-level → S3
+
+Block-level with cluster software → EBS Multi-Attach

Study_Notes/04_Ec2_STORAGE_EBS/03-ebs-snapshots.md

@@ -0,0 +1,43 @@
+EBS Snapshots are point-in-time backups of EBS volumes.
+
+Snapshots are stored in Amazon S3, but not directly accessible as S3 objects.
+
+# Snapshot behavior:
+
+First snapshot is full
+
+All subsequent snapshots are incremental
+
+Only changed blocks are saved
+
+Deleting a snapshot does not break others
+
+What snapshots enable:
+
+Disaster recovery
+
+Cross-region migration
+
+Volume cloning
+
+AMI creation
+
+# Operational details:
+
+Snapshots are regional
+
+Volumes created from snapshots can be in any AZ within the region
+
+Snapshots can be copied to other regions
+
+Important clarification:
+Snapshots back up the volume, not the EC2 instance.
+Memory, CPU state, and running processes are NOT captured.
+
+# Exam traps:
+
+Snapshots are not real-time replication
+
+Snapshots do not replace high availability
+
+Snapshots are not automatic unless configured

Study_Notes/04_Ec2_STORAGE_EBS/04-ami-overview.md

@@ -0,0 +1,48 @@
+An Amazon Machine Image (AMI) is a bootable template used to launch EC2 instances.
+
+# An AMI includes:
+
+Operating system
+
+Installed software
+
+Configuration settings
+
+One or more EBS snapshots
+
+# AMIs enable:
+
+Rapid instance launches
+
+Identical environments
+
+Auto Scaling
+
+Disaster recovery
+
+# ypes of AMIs:
+
+AWS-provided (Amazon Linux, Ubuntu, Windows)
+
+Marketplace AMIs
+
+Custom AMIs
+
+# Key distinction:
+
+Snapshot = disk backup
+
+AMI = launchable system template
+
+Lifecycle understanding:
+
+Create or modify EC2 instance
+
+Create AMI
+
+AMI references snapshots
+
+New EC2 instances launched from AMI
+
+# Exam mindset:
+If the question mentions preconfigured EC2 instances, think AMI.

Study_Notes/04_Ec2_STORAGE_EBS/05-ami-hands-on-and-image-builder.md

@@ -0,0 +1,44 @@
+Manual AMI creation is slow and error-prone.
+EC2 Image Builder exists to automate AMI creation and maintenance.
+
+# Image Builder automates:
+
+OS updates
+
+Security patches
+
+Software installation
+
+Testing
+
+AMI distribution
+
+# Core components:
+
+Image pipeline
+
+Build components
+
+Validation steps
+
+Scheduling
+
+# Why AWS built this:
+
+Enterprises need consistent images
+
+Security compliance requires repeatability
+
+Manual processes do not scale
+
+When to use Image Builder:
+
+Regular AMI updates
+
+Security-focused environments
+
+Large fleets of EC2 instances
+
+# Exam logic:
+Manual AMI = possible
+Automated AMI lifecycle = Image Builder

Study_Notes/04_Ec2_STORAGE_EBS/06-ec2-instance-store.md

@@ -0,0 +1,38 @@
+Instance Store is temporary storage physically attached to the EC2 host machine.
+
+# Key characteristics:
+
+Extremely high performance
+
+No additional cost
+
+Data is ephemeral
+
+Data is lost when:
+
+Instance stops
+
+Instance terminates
+
+Underlying hardware fails
+
+# Correct use cases:
+
+Caches
+
+Temporary files
+
+Scratch space
+
+Buffers
+
+# Incorrect use cases:
+
+Databases
+
+Backups
+
+Anything needing persistence
+
+# Exam rule:
+If the question says “data must survive restart”, Instance Store is wrong.

Study_Notes/04_Ec2_STORAGE_EBS/07-efs-overview.md

@@ -0,0 +1,30 @@
+Amazon Elastic File System (EFS) is managed shared file storage.
+
+# EFS characteristics:
+
+File-level storage
+
+Linux workloads
+
+Multiple EC2 instances can mount simultaneously
+
+Automatically scales
+
+Regional and multi-AZ
+
+# EFS vs EBS:
+
+EBS = single instance disk
+
+EFS = shared filesystem
+
+# Common uses:
+
+Shared web content
+
+Content management systems
+
+Shared application data
+
+# Exam logic:
+Multiple EC2 instances need shared access → EFS.

Study_Notes/04_Ec2_STORAGE_EBS/08-amazon-fsx-overview.md

@@ -0,0 +1,24 @@
+Amazon FSx provides fully managed file systems optimized for specific workloads.
+
+# FSx variants:
+
+FSx for Windows File Server
+
+FSx for Lustre
+
+# Why FSx exists:
+
+EFS is general-purpose
+
+Some workloads need specialized performance or compatibility
+
+# Use cases:
+
+Windows applications
+
+High-performance computing
+
+Media processing
+
+# Exam hint:
+If the workload mentions Windows file systems, think FSx.

Study_Notes/04_Ec2_STORAGE_EBS/09-shared-responsibility-ec2-storage.md

@@ -0,0 +1,27 @@
+AWS Shared Responsibility Model applies to EC2 storage.
+
+# AWS is responsible for:
+
+Physical data centers
+
+Hardware
+
+Underlying infrastructure
+
+Availability of services
+
+# You are responsible for:
+
+Data protection
+
+Backups
+
+Encryption configuration
+
+Access permissions
+
+Snapshot and AMI management
+
+# Critical exam takeaway:
+AWS secures the cloud.
+You secure what’s in the cloud.