{
  "id": 16243728,
  "title": "Created EBS volume for the first time",
  "url": "https://urgent.news/2026/10/23/created-ebs-volume-for-the-first-time",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-23T23:25:29.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/mohammed_mubashir_eb73cab/created-ebs-volume-for-the-first-time-2g8m"
  },
  "original_language": "en",
  "account": "I recently embarked on my journey to learn AWS and today marked a significant milestone as I successfully created my first Elastic Block Store (EBS) volume. Prior to this, I had only launched EC2 instances, but understanding the storage capabilities of EBS became crucial when considering data safety even in the event of an instance failure.\n\nEBS, also known as Elastic Block Store, functions as a virtual hard drive that can be attached to an EC2 instance. What sets it apart is that the data is stored independently from the instance, ensuring it remains intact even if the instance is stopped or terminated.\n\nTo create my EBS volume, I followed these steps:\n1. Launched an EC2 instance named \"mo\" in the eu-north-1b Availability Zone.\n2. Navigated to the EC2 dashboard, then to Volumes, and finally to Create Volume.\n3. Configured the volume to be 10 GB in size.\n4. Attached the newly created volume to my \"mo\" instance.\n5. Connected to the instance and verified the presence of the new disk using the command `lsblk`.\n\nBefore creating the volume, I mistakenly attached it to the same EU region but in a different Availability Zone (eu-north-1a). Consequently, when I attempted to attach the volume to my instance, it did not appear as an option. This was due to the fact that an EBS volume can only be attached to an instance within the same Availability Zone. Upon realizing this, I created a new volume in eu-north-1b and successfully attached it to my instance without any issues.\n\nThis experience taught me a valuable lesson: always verify the Availability Zone of your instance before creating an EBS volume. Unused volumes continue to incur costs, so it's essential to delete any incorrectly created volumes to avoid unnecessary expenses.\n\nAs someone who has worked with EBS, I'm curious to hear about any mistakes you made when you were first getting started. What's a common beginner error that you can recall?",
  "summary": "Created EBS volume for the first time I’ve been learning AWS, and today I created my first EBS volume. Until now I had only launched EC2 instances, so I wanted to understand how storage works when you need data to stay safe even if the instance goes away. What is EBS? Elastic Block Store (EBS) is like a virtual hard drive you can attach to an EC2 instance. The data lives separately from the…",
  "key_points": [
    "Created first EBS volume, marking learning milestone in AWS journey",
    "Configured 10 GB volume for EC2 instance mo in eu-north-1b Availability Zone",
    "Learned to verify Availability Zone before attaching volume to prevent errors"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}