![]() Meaning if you plan on making changes to your AMI at runtime that you’d like to see after a reboot, you need to attach a disk (EBS in Amazon AWS speak). Just in case you don’t know what EBS is good for – an Instance Store EC2 server doesn’t come with a disk for storing your data. With Ubuntu and RedHat distros to choose from, you can even use an AMI which launches via Elastic Block Storage (EBS) – how’s that for easy? Digging in a little deeper, I soon understood what all the hoopla was about and was soon sold on a nicely contained, pre-configured bitnami WordPress AMI. I’d never heard of it before and, truth be told, it actually sounded like some kind of BitTorrent client to me. ![]() My initial plan was to grab some Debian based Amazon Machine Image (AMI) and follow the various “howto config wordpress on lamp” posts out there, but Matthias asked if I’d had a look at bitnami. ![]() Without further ado, here’s how I migrated AWO to our first Amazon EC2 instance. As Matthias did the bulk of the joyent public cloud & linode migrations, it was high-time I got my hands dirty. Looking to save costs on our blog hosting, Amazon’s announcement of a 12 month free usage tier put us in the short list for migration. The cool thing about technical howtos like this is the ability to share with other folks who get just as excited.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |