The Wizard will even give you the option of locking this down to your current IP address which I certainly recommend for the initial setup & config.Ĭlick “Launch” and you’ll be prompted to create and/or download a public/private keypair in a.
The only change you’ll need to make to the default settings, is to add HTTP port 80 to the default security group. You’ll be automatically forwarded to the AWS Console for launching that instance in the desired region: Once you decide on a region and an instance type, just click on the desired bitnami WordPress AMI. We ultimately went with the mid-point “U.S. West Coast, but there are significant visits throughout the Continental U.S. If you’re using Google Analytics, checkout your “Audience -> Geo -> Location” to see the regions sending your blog the most visits.
You should definitely spend a few minutes considering the region in which to launch the instance.
UPDATE BITNAMI WORDPRESS STACK FREE
One of the catches for a 12 month, free EC2 instance is a new Amazon account, so be sure to register a new email address or you might get a surprise bill next month! And, yes, you will also need a valid credit card to open your account, because if your instance exceeds the free usage tier limits, you will be charged.įor those of you running multiple WordPress blogs, bitnami even offers preconfigured MultiSite AMIs! 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 kommentar(er)
