Advice for an EC2 Architecture and Deployment Strategy

Posted by Mark on Server Fault See other posts from Server Fault or by Mark
Published on 2014-08-21T22:08:01Z Indexed on 2014/08/21 22:21 UTC
Read the original article Hit count: 191

My company is currently migrating several websites and PHP web applications (standard LAMP stack) from three in-house servers to Amazon EC2. Because we had only three servers, we clustered several low-traffic websites with perhaps one high-traffic web application, and served them from the same server. The server admin has pretty much copied the previous architecture wholesale onto the EC2 instances, simply upping the instance size to account for the highest traffic client that occupies that particular instance.

This architecture might be okay if it wasn't for deployment. Any time one of these sites/apps changes, it means redeploying the entire instance, along with the 30 sites/apps it hosts, instead of just updating one.

How can we architect our cloud in a more modular fashion? Should each app get its own appropriately-sized instance? What is the best strategy for deployment in this type of situation?

© Server Fault or respective owner

Related posts about amazon-ec2

Related posts about deployment