Hey cloud explorers! Welcome back to another episode of Cloud in List of Threes (CiLoTs) ☁️3️⃣, where we break down complex cloud concepts into bite-sized pieces, seasoned with fun analogies! 🤩 Today, we're taking a trip into the world of cloud storage. ☁️🗄️ We'll explore three popular AWS storage solutions: S3, EBS, and EFS!
Amazon S3 (Simple Storage Service) ☁️🗄️
Imagine a massive, secure storage warehouse. 🏢 You can rent a unit (bucket) to store anything you want: photos, videos, documents, even old furniture! 📦 You can access your stuff from anywhere in the world, and you only pay for the space you use. 🌍💰
Technical translation 👨🏿💻: Amazon S3 is an object storage, meaning it stores data as individual objects in buckets. It's highly scalable, durable, and cost-effective. Each object has its own unique ID and metadata and is organized into containers called buckets. Buckets help manage and group objects, providing kind of like a hierarchical structure for your data. Basically, S3 allows you to store any type of data (text, blob, video, audio, etc) in a highly scalable, durable, and cost-effective manner.
Three Key Benefits:
Durability: Your data is safe and secure, with multiple copies stored across different locations. 💪
Scalability: Store as much or as little as you need, and easily adjust your storage capacity. 📈
Accessibility: Access your data from anywhere with an internet connection. 🌐
Amazon EBS (Elastic Block Storage) 💾💻
Think of EBS as an extra external hard drive you can attach to your computer (EC2 instance). It's like having more space to store your operating system, applications, and files. 💽 You can even choose different types of hard drives depending on your needs (speed, performance).
Technical translation 👨🏿💻: Amazon EBS offers block-level storage volumes, which function similarly to individual hard drives. These volumes can be attached to Amazon EC2 instances, providing the operating system and applications with persistent storage. EBS offers various volume types (SSD-based and HDD-based), each optimized for specific performance needs such as throughput and IOPS (input/output operations per second). This allows you to customize your storage based on the requirements of your applications.
Three Key Benefits:
Persistence: Your data remains on the volume even if you unplug the hard drive or restart your computer/EC2. 🔄
Flexibility: Choose from different volume types — SSD-based and HDD-based to optimize performance and cost. ⚙️
Integration: Seamlessly integrates with EC2 for easy management. 🤝
Amazon EFS (Elastic File System) 📁🔗
Imagine a toy box that you and your friends can all share. 🪀🗃️You can put your toys in it, and your friends can take them out to play with them. You can all play with the same toys at the same time without fighting over them! That's kind of like what Amazon EFS does for computers in the cloud.
Technical translation 👨🏿💻: EFS offers a network file system that can be accessed concurrently by multiple Amazon EC2 instances. This shared access facilitates collaboration and data sharing among different parts of your application.
Three Key Benefits:
Scalability: Automatically grows and shrinks as your storage needs change. 📈
Shared Access: Multiple services and instances can access the file system simultaneously. 🧑🤝🧑
Elasticity: Pay only for the storage you use, and scale your capacity as needed. 💰
And there you have it, folks! We've now learned how to store your stuff in the cloud (AWS). Whether you need a massive warehouse, an extra hard drive, or a shared file system, AWS has the perfect storage solution for you. Stay tuned for more cloud adventures in the next episode of Cloud in List of Threes! ☁️3️⃣
Check out the previous episode here.
#CloudComputing #AWS #S3 #EBS #EFS #CiLoTs #CiLoTsEp04
Top comments (1)
Great breakdown of S3 vs EBS vs EFS. The decision matrix is sharper when you bring in real workloads:
EBS is a block device, not shared — single EC2 instance, single AZ, gp3/io2. EFS is NFS-mounted across AZs but charged per-GB used. S3 is object + 11 nines durability. Picking the wrong one costs you either money (over-provisioned EBS for shared access) or performance (S3 mounted as a drive letter for random-write workloads).
EFS vs FSx for Windows — EFS is NFS-only; for Windows file-server workloads, FSx for Windows File Server is the right answer. The blog calls out EFS as 'Windows-compatible' which is technically true but operationally misleading.
S3 Inventory for cost clarity — once a bucket grows past 10M objects, S3 Inventory (CSV/Parquet reports on schedule) is the only way to actually answer 'where is our money'. Athena queries on the inventory file give per-prefix storage class breakdown that the console cannot.
Mount layer for Windows-side ops on S3 buckets: ScsDriver