Chapter 2. Starting with EC2, RDS, and S3/CloudFront
So far we have talked about AWS. You have seen where it comes from, how it can help you with growing your application, and how a virtual infrastructure on AWS benefits your work. It is important to understand the context, because it helps you select the services and tools you need to move your app to AWS. But real experience only comes with practice!
So let’s get down to business. First off, you need an AWS account, which requires a valid credit card and a phone. Once you have an account, all AWS services are at your disposal. To use the services, you need to set up your local environment for working with the command-line tools in case you need them. For now, the AWS Console and command-line tools are enough, but there are commercial and noncommercial applications and services available that offer something extra. Last, but not least, you might want to monitor your application and get tools to fix it on the move as well.
With the account activated and the tools available, all we need is an application to build. Working on a real application is more fun than just a demo, so we’ll use one of our applications in production, called Kulitzer. Kulitzer.com calls itself “the contest platform for creative people. You can join a contest, enter your work, and take a seat in the jury. Can’t find any contest you like? Start your own!” Kulitzer is a Rails application, developed in New Zealand by Arjan van Woensel. Very early in the process, ...