ec2base

http://www.freesoftwaremagazine.com/columns/talk_brandon_whichard_about_zenoss_cloud_amazons_ec2_and_more

This sounds like a dream: you are running out of CPU power? Easy, within 10 minutes you have another server ready to roll. However, it’s not really that simple. Unless you did things right, a new server won’t go very far — it needs to be configured to do the right thing. For example if your web server is under too much stress, and you add a server, the second one needs to be in the pool of daemons which serve web pages; more importantly, it needs to be able to access the data (database and files) in order to do that. So, realistically you will have a database server, a file server, a main web server which will act as a proxy, and a pool of web servers which will access data from the shared file system and the database server(s). Such a setup is common but it’s not as straightforward as it might sound. You might decide to have only one database server, and use memcached instead — therefore having a second pool of servers. No, it’s not for everybody. I pointed this out to Whichard. He said “Yeah, you are totally right. You definitely will need a script that will configure the new server and will get it to do something useful. The setup you mentioned [with a reverse proxy server dispatching HTTP requests to sub-servers] is the most common one; thing is, now there is the technology to do this. It might not be easy (well, not yet) but it’s definitely possible.

http://groups.drupal.org/pantheon/mercurywiki

By popular request, here are step-by-step instructions for building the Project Mercury setup on a fresh ec2 image. We have both 32 and 64 bit versions of this AMI available (see http://groups.drupal.org/amazon-web-services-s3-ec2).

http://www.ardentsoft.com/blog/tag/lamp-on-ec2

Part 1: Setting up Amazon Web Services
Part 2: Setting up a Persistent Volume
Part 3: Starting and Configuring the Instance
Part 4: Mounting a Persistent Volume
Part 5: Configuring MySQL
Part 6: Configuring Apache
Part 7: Configuring PHP
Part 8: Setting up an Elastic IP Address
Part 9: Setting up Snapshots
Part 10: Generating a Custom AMI

http://www.rayacayan.com/blog/projects/the-amazon-ec2-blog-migration-project/

This side project presents my procedure for migrating my WordPress blog from a web hosting provider running cPanel to an Amazon EC2 instance.

This project builds on the environment created in my previous blog post, “The Mobile Cloud Project, Part 1.1: Basic AWS”, where I presented an overview of Amazon Web Services and a procedure for creating virtual servers (Reserved and On-Demand instances) on Amazon EC2.

http://www.mikebrittain.com/blog/2008/07/19/web-hosting-on-ec2/

In the months prior to leaving Heavy, I led an exciting project to build a hosting platform for our online products on top of Amazon’s Elastic Compute Cloud (EC2). We eventually launched our newest product at Heavy using EC2 as the primary hosting platform.

What follows is a general outline of how we do this.

http://stackoverflow.com/questions/1597930/architecture-of-a-php-app-on-amazon-ec2

But what’s the next logical step that is going to yield good results for scalability? Do I fire up an AMI instance for the MySQL and one for the Apache service? Or do I just replicate the instances out as many times as I need them and then do some sort of load balancing on the front end? Ideally, I’d like to have a centralized database because I do aggregate statistics across all database rows, however, this is not a hard requirement (there are probably some application specific solutions I could come up with to work around this)

http://vasyas.blogspot.com/2008/10/amazon-ec2-amazon-ebs-java-mysql.html

Устанавливаем на Amazon EC2 и Amazon EBS Java-приложение с MySQL

http://vastpark.posterous.com/moving-to-amazon-web-services

I have been administrating LAMP web servers in some form or another for more than a decade either in support of a business or for personal use. I seem to never have so few projects that shared hosting made sense. So instead, solutions like virtual private servers, managed dedicated hosting and, in some cases, my own rack of equipment have served up my projects over the years.

Most recently I had been using dedicated managed servers on Rackspace and GoDaddy to host a few dozen sites. Because I no longer run my own DNS or mail servers, it made my migration focused on making MySQL and Apache work on AWS. (I no longer host DNS or mail because as I have found services like EveryDNS and Gmail to be far superior.)

http://www.john-nousis.com/development/tutorial-running-a-phpmysql-server-on-ec2-with-ebs/

During the presentation I showed how you can start an AMI of fedora 8 base, install apache, php and mySQL and make them all store their data on an EBS volume. This attracted a lot of attention and participants asked me to post this as an online tutorial. This tutorial requires basic knowledge of AWS like running an EC2 instance, creating an EBS volume and assigning an elastic IP to the instance. During the presentation I used ElasticFox which is a firefox plugin that allows you to perform several operations on Amazon through a graphical user interface.

http://stackoverflow.com/questions/1530613/recommended-ec2-ami-for-high-traffic-php-web-service

What AMI is recommended for my setting (high traffic PHP web service?) It needs to support millions of requests a day. I need an OS that can be easily maintained by non expert + NGinx and my entire configuration + Security and other essential management features.

Simple question. No answers.

http://www.livingdigitally.net/2009/04/tips-for-deploying-a-lamp-stack-on-amazon-ec2.html

If you’re interested in using Amazon EC2 and other services to deploy a LAMP (Linux, Apache, MySQL, and PHP) stack, you will probably find this post invaluable. I spent about three full days migrating all my sites over from a physical dedicated server to an EC2 instance, and what follows are several things I learned during the process.