Configuring AWS Auto Scaling for WordPressIn previous posts, we covered the basics of Amazon Web Services, Preparing AWS Services to support our sample WordPress workload, and Installing WordPress in AWS with ElastiCache and S3/Glacier backups. In this post we’ll look at how to configure an AWS Auto Scaling group of WordPress servers that respond dynamically to the load placed on them by creating new EC2 instances on demand, or spinning down unnecessary instances during low demand to save on operational expenses. Auto Scaling uses AWS Cloud Watch to monitor AWS components and responds to alarm metrics (CPU utilization, number of connections, etc.).
Preparing Amazon Web Services (AWS) for an Auto-Scaling WordPress Site
In my last article I covered the basics of Amazon Web Services (AWS). Now it’s time for some hands-on configuration. The example I’ll be working with in the next few posts is a WordPress based site. I’ll leverage a bunch of services within AWS to support my site – Route 53 for DNS, RDS (MySQL as a Service), Elastic Load Balancers in front of auto-scaling EC2 instances (monitored by CloudWatch), ElastiCache, Simple Storage Services (S3), and CloudFront. As you can see, this setup will be very different from the shared hosting or VPS server you might be on today. Taking advantage of these different AWS services lets me scale much easier (and automatically) than just installing everything on a single server.
Introduction to Amazon Web Services (AWS)As Virtualization Practice Manager, I spend most of my time focused on the VMware stack, but I’m also working with various other technologies including Amazon Web Services. Many Clearpath customers are expressing interest in hybrid cloud to support their evolving architectures, applications, and business requirements. As a value added reseller (VAR), Clearpath is in a unique position to guide customers through the transition to a hybrid cloud through our strong partnerships with VMware, Cisco, EMC, and Amazon Web Services. By drawing on our history of providing private cloud architectures based on VMware, Cisco and EMC, our experience as a cloud service provider, and our multidisciplinary team of engineers we help customers put the right workload in the right cloud at the right time.
We recently covered the launch of VMware’s Horizon Suite of End User Computing (EUC) products, including VMware Horizon View, VMware Horizon Mirage, and VMware Horizon Workspace. The products present a set of tools that enable IT to exercise comprehensive end-point management while delivering a unified user experience across a variety of devices and access methods.
EMC showed off ViPR (previously known as Project Bourne) at EMC World 2013. ViPR is EMC’s solution for Software Defined Storage (SDS), helping to round out the EMC² family’s (EMC, VMware, Pivotal, RSA) Software Defined Data Center (SDDC) vision. Dave provided our introductory coverage of ViPR here. Since being unveiled at EMC World, I’ve heard some confusion in social media circles over what exactly ViPR is – along the lines of ‘ask 10 people what ViPR is and get 10 different answers’. To try to clear up some confusion, here is a brief overview of ViPR.
At EMC World yesterday, the newly formed joint venture between EMC and VMware, along with a strategic investment by General Electric (GE) was discussed by Paul Maritz (former VMware CEO) in the morning’s keynote address. Pivotal combines intellectual property and engineering resources (1200 employees) from both EMC and VMware to focus on solving big and fast data problems. Pivotal combines solutions such as EMC Greenplum and VMware Cetas to serve and analyze ‘Big Data’, VMware Gemfire to rapidly ingest ‘Fast Data’, VMware’s Spring and vFabric technologies, and Pivotal Labs software for rapid application development and integration, with the underlying support of VMware Cloud Foundry.