Deploying a Sinatra Application to AWS Elastic Beanstalk
This walkthrough shows how to deploy a simple Sinatra web application to AWS Elastic Beanstalk using the Elastic Beanstalk Command Line Interface (EB CLI).
Creating environments with the EB CLI requires a service role. You can create a service role by creating an environment in the Elastic Beanstalk
Management Console. If you don't have a service role, the EB CLI will attempt to create one when
This walkthrough requires a Linux, Windows or OS X workstation. Performing the walkthrough will modify your workstation's Git and EB CLI configuration. If you do not want to modify your workstation's configuration for the walkthrough, you can use one of the following:
An instance running in a virtual machine on your workstation.
An Amazon Elastic Compute Cloud (Amazon EC2) instance.
Use SSH to log in to the instance. You can perform the entire walkthrough from the command line. When you have finished, you can terminate the instance.
The following tools are required to complete this walkthrough:
The EB CLI, installed as described in Install the Elastic Beanstalk Command Line Interface (EB CLI).
This topic also describes how to sign up for an AWS account, if you do not have one.
AWS credentials that have permissions to create the AWS resources that make up the application's environment on your system.
These credentials allow the EB CLI to act on your behalf to create the environment's resources. If you do not have stored credentials, the EB CLI prompts you for credentials when you create the application. For more information on how to store credentials and how the EB CLI handles stored credentials, see Configuration Settings and Precedence. For more information on the required permissions, see Using Elastic Beanstalk with AWS Identity and Access Management.
For Linux systems, you can use the package manager to install Git. For example, the following command installs Git on Debian-family Linux systems, such as Ubuntu.
sudo apt-get install git
For Red Hat-family systems, you can use the same command, but you use the package manager name
yum. For more information, including directions for installing Git on OS X systems, see git.
Step 1: Set Up Your Project
With the EB CLI, you can quickly create an Elastic Beanstalk environment and deploy applications to that environment from a Git repository. Before starting your first project, set up the example project for the walkthrough.
To set up the example project
Open a terminal window and create a directory for your project in a convenient location on your system. This walkthrough assumes that the directory is named
Move to the
sinatraappdirectory and initialize a Git repository.
git init .
You do not need to have access to a remote repository, such as GitHub, for this walkthrough. The walkthrough uses a local Git repository.
If this is your first time using Git, add your user name and email address to the Git configuration so you can commit changes.
git config --global user.email "$
git config --global user.name "
Step 2: Create an Application
Now create an application and its associated environment.
To create an application
sinatraappdirectory, create the application by running the following command.
Choose the default AWS region. For this walkthrough, choose US-West-2.
Select a default region 1) us-east-1 : US East (N. Virginia) 2) us-west-1 : US West (N. California) 3) us-west-2 : US West (Oregon) 4) eu-west-1 : EU (Ireland) 5) eu-central-1 : EU (Frankfurt) 6) ap-southeast-1 : Asia Pacific (Singapore) 7) ap-southeast-2 : Asia Pacific (Sydney) 8) ap-northeast-1 : Asia Pacific (Tokyo) 9) sa-east-1 : South America (Sao Paulo) (default is 3):
If you have previously configured a default region with the EB CLI, the AWS CLI or an SDK, the EB CLI skips this step and creates the application in the default region unless you explicitly specify a region with the
We strongly recommend that you do not provide your account's root credentials to Elastic Beanstalk. Instead, create an AWS Identity and Access Management (IAM) user with appropriate permissions and provide those credentials. For more information on managing AWS credentials, see Best Practices for Managing AWS Access Keys.
If you do not have stored credentials, or your stored credentials do not grant the correct permissions,
eb initprompts you for credentials, as follows:
You have not yet set up your credentials or your credentials are incorrect You must provide your credentials. (aws-access-id):
Elastic Beanstalk then stores these credentials in the AWS CLI
configfile with a profile name of
Enter your application name. For this walkthrough, use the default value, which is the application's root directory name.
Enter Application Name (default is "sinatraapp"):
Specify your platform. For this walkthrough, use Ruby.
Select a platform. 1) PHP 2) Node.js 3) IIS 4) Tomcat 5) Python 6) Ruby 7) Docker 8) GlassFish 9) Go (default is 1):
Specify the platform version. For this example, use Ruby 2.1 (Puma).
Select a platform version.1 1) Ruby 2.1 (Puma) 2) Ruby 2.1 (Passenger Standalone) 3) Ruby 2.0 (Puma) 4) Ruby 2.0 (Passenger Standalone) 5) Ruby 1.9.3 (default is 1):
Specify whether you want to use SSH to log in to your instances. You won't need to log in to your instances for this walkthrough, so enter
Do you want to set up SSH for your instances? (y/n):
Step 3: Create an Environment
Next, create an Elastic Beanstalk environment and deploy a sample application to it with
eb create sinatraapp-dev --sample
If you see a "service role required" error message, run
eb create interactively
(without specifying an environment name) and the EB CLI will create the role for you.
With just one command, the EB CLI sets up all of the resources our application needs to run in AWS, including the following:
An Amazon S3 bucket to store environment data
A load balancer to distribute traffic to the web server(s)
A security group to allow incoming web traffic
An Auto Scaling group to adjust the number of servers in response to load changes
Amazon CloudWatch alarms that notify the Auto Scaling group when load is low or high
An Amazon EC2 instance hosting our application
When the process is complete, the EB CLI outputs the public DNS name of the application
eb open to open the website in the default browser:
Step 4: Deploy a Simple Sinatra Application
You can now create and deploy a Sinatra application. This step describes how to implement
a simple Sinatra application and deploy it to the environment that you created in the
preceding step. Our example implements a classic application that prints a simple text string,
Hello World!. You can easily extend this example to implement more complex
classic applications or modular applications.
Create all of the application files in the following procedure in the application's root
To create and deploy a Sinatra application
Create a configuration file named config.ru with the following contents.
require './helloworld' run Sinatra::Application
Create a Ruby code file named helloworld.rb with the following contents.
require 'sinatra' get '/' do "Hello World!" end
Create a Gemfile with the following contents.
source 'http://rubygems.org' gem 'sinatra'
Add your files to the Git repository and then commit your changes, as follows:
git add .~/sinatraapp$
git commit -m "Add a simple Sinatra application"
You should see output similar to the following indicating that your files were successfully committed.
[master (root-commit) dcdfe6c] Add a simple Sinatra application 4 files changed, 13 insertions(+) create mode 100644 .gitignore create mode 100644 Gemfile create mode 100644 config.ru create mode 100644 helloworld.rb
The files are committed to the current Git branch. Because you have not yet explicitly created any branches, the files are committed to the default branch, which is named
master. If the repository has multiple branches, you can configure Git to push each branch to a different environment. For more information, see Managing Elastic Beanstalk Environments with the EB CLI.
Deploy the new Sinatra application to the environment.
eb deploycommand creates a bundle of the application code in the master branch and deploys it to the environment, replacing the default application. The second deployment should be much faster than the first because you have already created the environment's AWS resources.
eb status --verbosecommand to check your environment status. You should see output similar to the following.
eb status --verboseEnvironment details for: sinatraapp-dev Application name: sinatraapp Region: us-west-2 Deployed Version: dcdf Environment ID: e-kn7feaqre2 Platform: 64bit Amazon Linux 2014.09 v1.2.0 running Ruby 2.1 (Puma) Tier: WebServer-Standard CNAME: sinatraapp-dev.elasticbeanstalk.com Updated: 2015-03-03 23:15:19.183000+00:00 Status: Ready Health: Green Running instances: 1 i-c2e712cf: InService
Repeat the command until Status is Ready and Health is Green. Then, refresh your browser or run
eb openagain to view the updated application, which should display
For a detailed description of the deployment, you can display the deployment log by
Step 5: Clean Up
When you have finished, you can terminate the application's environment by running the
following command from the root directory,
This command shuts down all of the environment's AWS resources, so you do not incur further charges. It typically takes a few minutes. When the process is complete, Elastic Beanstalk displays the following message.
INFO: terminateEnvironment completed successfully.
If you have attached an Amazon Relational Database Service (Amazon RDS) database instance to your environment, termination deletes the instance. If you want to save your data, create a snapshot before terminating the environment. For more information, see Creating a DB Snapshot. For more information about using Amazon RDS with Elastic Beanstalk, see Using Amazon RDS with Ruby.