Chapter 2. A simple example: WordPress in five minutes

This chapter covers:

  • Creating a blogging infrastructure
  • Analyzing costs of a blogging infrastructure
  • Exploring a blogging infrastructure
  • Shutting down a blogging infrastructure

In chapter 1, we looked at why AWS is such a great choice to run web applications in the cloud. In this chapter, you’ll evaluate migrating the blogging infrastructure of your imaginary company to AWS.

Example is 100% covered by the Free Tier

The example in this chapter is covered by the Free Tier. As long as you don’t run this example longer than a few days, you won’t pay anything for it. Keep in mind that this applies only if you created a fresh AWS account for this book and there are no other things going on in your AWS account. Try to complete the chapter within a few days, because you’ll clean up your account at the end of the chapter.

Your imaginary company currently uses WordPress to host over 1,000 blogs on your own servers. The blogging infrastructure must be highly available, because customers don’t tolerate outages. To evaluate whether a migration is possible, you need to do the following:

  • Set up a highly available blogging infrastructure
  • Estimate monthly costs of the infrastructure

WordPress is written in PHP and uses a MySQL database to store data. Apache is used as the web server to serve the pages. With this information in mind, it’s time to map your requirements to AWS services.

2.1. Creating your infrastructure

2.2. Exploring your infrastructure

2.3. How much does it cost?

2.4. Deleting your infrastructure

2.5. Summary