This guide will walk you though the details of deploying a plain-vanilla Linux, Apache, MySQL, PHP (LAMP) application in the Amazon Web Services (AWS) cloud. If you've never used the cloud before, or don't understand how some of the various components relate to each other, then this article is a great place to start. The cloud components we'll be using throughout this guide are Amazon's Elastic Compute Cloud (EC2), Simple Storage Service (S3), Auto Scaling, Elastic Load Balancing, and Relational Database Service.
In the previous article on the subject of cloud computing using AWS, we setup a simple LAMP application that used a single web server to present data that was queried from a single RDS instance. In this guide we will see how to save the changes we made to the EC2 instance, create more EC2 instances, and setup load balancing across our web servers.
The purpose of this guide is to convey a basic understanding of how to manipulate data that is stored within an LDAP server. It does not speak to setting up the server, configuring the LDAP service itself, or securing the LDAP server. For information on these topics, see 
Just as using IMAP instead of POP3 allows you to keep your messages in one place (the server) while using as many different email clients as you wish, so too does putting your address book in LDAP free you from having your contacts in only one program, and on only one computer. However, quite unlike using a straightforward protocol like IMAP, actually implementing and then using the Lightweight Directory Access Protocol is anything but easy. Here I share what I've learned in getting LDAP + TLS (SSL) up and working for both Evolution on Ubuntu Linux and Horde on CentOS Linux.
This is a perennial favorite in technical interviews: "so you type 'www.example.com' in your favorite web browser. In as much detail as you can, tell me what happens."
One thing that is critical for any Puppet deployment is monitoring. Experience has shown that while the Puppetmaster server process is usually quite stable, the Puppet client daemons will, on occasion, die unexpectedly. This article will give an overview of how to setup monitoring of both the Puppetmaster server itself and all of the Puppet clients.
Configuration and change management are extremely important in keeping a production environment running smoothly with high uptime. Puppet does a fantastic job of distributing and enforcing configurations, while Subversion is good for keeping an audit trail of configuration changes. Putting the two together gives you a world-class solution that easily scales into the tens of thousands of servers.
The MySQL web site has a pretty decent 
