关于MongoDB部署选型及EC2挂载独立EBS卷存数据的咨询

Hey there, great call going with EC2 self-hosted for your use case—persisting your MongoDB data on a separate EBS volume is totally doable, and it’ll let you terminate/replace instances without losing a thing. Let’s break this down into actionable steps tailored to your m5.large instance:

Step 1: Create a Persistent EBS SSD Volume #

First, you need to spin up an EBS volume that won’t get deleted when your EC2 instance terminates:

• Head to the AWS EC2 Console, go to Volumes under Elastic Block Store.
• Click Create volume:
  • Pick an SSD type (gp3 is the default and cost-effective for most workloads; go with io2 if you need higher IOPS or durability).
  • Set the size based on your MongoDB storage needs (start with what you need, you can resize later).
  • Critical: Make sure the volume is in the same Availability Zone (AZ) as your m5.large instance—EBS volumes are AZ-specific.
  • Under Additional settings, uncheck the Delete on termination option. This ensures the volume sticks around even if your instance is terminated.
• Click Create volume to finish.

Step 2: Attach & Mount the EBS Volume to Your EC2 Instance #

Next, attach the volume to your running m5.large instance and get it ready for MongoDB:

1. In the EC2 Console, select your new EBS volume, click Actions > Attach volume, then choose your m5.large instance from the dropdown. Note the device name (it’ll look like /dev/nvme1n1 for Nitro-based instances like m5.large).
2. SSH into your EC2 instance. First, list all block devices to confirm the new volume is detected:

   lsblk
   

   You should see your new volume (e.g., nvme1n1) listed without a mount point.
3. If this is a brand-new volume, you’ll need to format it with ext4 (skip this if you’re reusing an existing volume with data):

   sudo mkfs.ext4 /dev/nvme1n1
   

4. Create a directory where MongoDB will store its data:

   sudo mkdir -p /data/mongodb
   

5. Mount the EBS volume to this directory:

   sudo mount /dev/nvme1n1 /data/mongodb
   

6. Give the MongoDB user ownership of the directory so it can read/write data:

   sudo chown -R mongodb:mongodb /data/mongodb
   

Step 3: Configure MongoDB to Use the EBS Volume #

Now update MongoDB’s configuration to point to the new storage path:

1. Open MongoDB’s config file (location varies by OS—on Amazon Linux 2 or Ubuntu it’s usually /etc/mongod.conf):

   sudo nano /etc/mongod.conf
   

2. Find the storage section, then modify the dbPath value to /data/mongodb:

   storage:
     dbPath: /data/mongodb
     # Keep other storage settings as-is
   

3. Save and exit the editor (Ctrl+O, then Ctrl+X in nano).
4. Restart the MongoDB service to apply the changes:

   sudo systemctl restart mongod
   

5. Verify the change worked by checking MongoDB’s active dbPath:
   • Log into the MongoDB shell: mongosh
   • Run this command to confirm the path:

     db.adminCommand({ getCmdLineOpts: 1 }).parsed.storage.dbPath
     

   You should see /data/mongodb returned.

Step 4: Ensure the Volume Mounts Automatically on Instance Reboot #

Right now, the volume will unmount if you reboot the instance. Fix this by adding it to /etc/fstab:

1. Get the UUID of your EBS volume (more reliable than device names, which can change):

   sudo blkid /dev/nvme1n1
   

   Copy the UUID string (looks like UUID=abc123-def456...).
2. Open /etc/fstab in an editor:

   sudo nano /etc/fstab
   

3. Add this line at the end (replace the UUID with yours):

   UUID=abc123-def456-ghi789-jkl012 /data/mongodb ext4 defaults,nofail 0 2
   

   The nofail option ensures the instance boots even if the volume can’t be mounted (prevents boot failures).
4. Test the fstab entry to make sure it works:

   sudo mount -a
   

   If no errors pop up, you’re good to go.

Step 5: Reattach the Volume to a New EC2 Instance (When You Terminate the Old One) #

When you’re ready to replace your m5.large instance:

1. Terminate the old instance—your EBS volume will remain intact because you disabled "Delete on termination".
2. Launch a new m5.large instance in the same AZ as your EBS volume.
3. In the EC2 Console, select your EBS volume, click Actions > Attach volume, and choose the new instance.
4. SSH into the new instance, then repeat steps 2 (mount the volume—skip formatting since it already has data) and 3 (configure MongoDB’s dbPath to /data/mongodb) from above.
5. Restart MongoDB, and your data will be exactly where you left it.

Quick Notes to Avoid Headaches #

• Backup First: Before making any changes, take a MongoDB dump (mongodump) or an EBS snapshot—better safe than sorry.
• OS Consistency: Make sure your new EC2 instance uses the same OS as the old one (e.g., Amazon Linux 2 → Amazon Linux 2) to avoid filesystem compatibility issues.
• IOPS Considerations: If your MongoDB workload is heavy, adjust the EBS volume’s IOPS during creation or later via the AWS Console to match your needs.

内容的提问来源于stack exchange，提问作者hardy