0

basically I want to setup an EC2 instance that is properly setup with LVM, instead of what you get when you start up one using the basic Ubuntu AMI which is completely un-partitioned.

Where I'm running into trouble though is the lack of a gui installer so I can set up the partitions before the first boot. This is my first time working in AWS, and I'm not familiar with how you'd set all this up after the fact.

Should I add an EBS volume and fully partition that? How would I then boot from that volume?

Or should I just set up the server in a virtual box, then create the AMI from that and create an instance from it in AWS?

What's the best way forward here?

Whitewind617
  • 113
  • 3
  • 1
    You need to describe what are you trying to solve with LVM. Otherwise, the best way is to leave it as is. – AlexD Dec 29 '21 at 08:54

1 Answers1

1

I looked into this when I was first using the cloud in order to apply CIS-hardened partition layouts. Long story short, messing with the root volume is simply not recommended. I came to the conclusion that given the 'cattle not pets' approach to the cloud, if something goes wrong I'll ditch the instance and deploy another fresh one, then investigate what used up my disk space in the first place.

The best advice I would give is if you particularly want seperate partitions/volumes, then create additional EBS volumes and attach them to your instance. YMMV when it comes to getting data synced up though, if you want to mount over something like /var. This approach works fine for things like home directories, but less so for system ones.

I would also look into building your own AMI as that may give you more control. Packer is an excellent tool for that.

shearn89
  • 3,403
  • 2
  • 15
  • 39