Elastic Beanstalk Developer Guide

Elastic Beanstalk

Developer Guide

API Version 2010-12-01

Elastic Beanstalk: Developer Guide

The following are trademarks of Amazon Web Services, Inc.: Amazon, Amazon Web Services Design, AWS, Amazon CloudFront,

AWS CloudTrail, AWS CodeDeploy, Amazon Cognito, Amazon DevPay, DynamoDB, ElastiCache, Amazon EC2, Amazon Elastic

Compute Cloud, Amazon Glacier, Amazon Kinesis, Kindle, Kindle Fire, AWS Marketplace Design, Mechanical Turk, Amazon Redshift,

Amazon Route 53, Amazon S3, Amazon VPC, and Amazon WorkDocs. In addition, Amazon.com graphics, logos, page headers,

button icons, scripts, and service names are trademarks, or trade dress of Amazon in the U.S. and/or other countries. Amazon's

trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is

likely to cause confusion among customers, or in any manner that disparages or discredits Amazon.

All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected

to, or sponsored by Amazon.

Elastic Beanstalk Developer Guide

Table of Contents

What Is Elastic Beanstalk and Why Do I Need It? ................................................................................ 1

Storage ............................................................................................................................... 2

Pricing ................................................................................................................................. 2

Community ........................................................................................................................... 2

Where to Go Next .................................................................................................................. 3

Getting Started ............................................................................................................................. 4

Walkthrough ......................................................................................................................... 4

Step 1: Sign up for the Service ......................................................................................... 4

Step 2: Create an Application .......................................................................................... 5

Step 3: View Information About Your Environment ................................................................ 6

Step 4: Deploy New Version ............................................................................................ 7

Step 5: Change Configuration .......................................................................................... 8

Step 6: Clean Up ......................................................................................................... 10

Accessing Elastic Beanstalk .................................................................................................. 11

AWS Management Console ........................................................................................... 12

Git Deployment Via Eb .................................................................................................. 12

AWS SDK for Java ....................................................................................................... 12

AWS Toolkit for Eclipse ................................................................................................. 12

AWS SDK for .NET ...................................................................................................... 13

AWS Toolkit for Visual Studio ......................................................................................... 13

AWS SDK for Node.js ................................................................................................... 13

AWS SDK for PHP ....................................................................................................... 13

Boto (AWS SDK for Python) .......................................................................................... 13

AWS SDK for Ruby ...................................................................................................... 14

Elastic Beanstalk API ................................................................................................... 14

Endpoints ................................................................................................................... 14

Where to Go Next ................................................................................................................ 14

How Does Elastic Beanstalk Work? ................................................................................................. 15

Components ....................................................................................................................... 15

Application ................................................................................................................. 15

Application Version ....................................................................................................... 15

Environment ............................................................................................................... 16

Environment Configuration ............................................................................................ 16

Configuration Template ................................................................................................. 16

Architectural Overview .......................................................................................................... 16

Web Server Environment Tiers ....................................................................................... 16

Worker Environment Tiers ............................................................................................. 18

Supported Platforms ............................................................................................................ 19

Docker ....................................................................................................................... 19

Docker - Preconfigured ................................................................................................. 22

Java .......................................................................................................................... 27

Windows and .NET ...................................................................................................... 32

Node.js ...................................................................................................................... 33

PHP .......................................................................................................................... 41

Python ....................................................................................................................... 46

Ruby ......................................................................................................................... 50

Design Considerations .......................................................................................................... 58

Scalability ................................................................................................................... 58

Security ..................................................................................................................... 58

Persistent Storage ....................................................................................................... 59

Fault Tolerance ............................................................................................................ 59

Content Delivery .......................................................................................................... 59

Software Updates and Patching ..................................................................................... 59

Connectivity ................................................................................................................ 59

Where to Go Next ................................................................................................................ 60

API Version 2010-12-01

iii

Elastic Beanstalk Developer Guide

Applications from Docker Containers ............................................................................................... 61

Single Container Docker Using the Console ............................................................................. 62

Single Container Docker Using Eb .......................................................................................... 63

Set Up Eb .................................................................................................................. 64

Configure Elastic Beanstalk Using Eb .............................................................................. 66

Create an Application ................................................................................................... 67

Single Container Docker Configurations ................................................................................... 68

Dockerfile ................................................................................................................... 68

Dockerrun.aws.json ...................................................................................................... 69

Multicontainer Docker Environments ....................................................................................... 71

Multicontainer Docker Platform ....................................................................................... 71

Dockerrun.aws.json File ................................................................................................ 72

Docker Images ............................................................................................................ 72

Container Instance Role ............................................................................................... 73

Amazon ECS Resources Created by Elastic Beanstalk ....................................................... 73

Using Multiple Elastic Load Balancing Listeners ................................................................ 74

Multicontainer Docker Configuration ........................................................................................ 75

Dockerrun.aws.json Format ........................................................................................... 75

Tutorial - Multicontainer Docker .............................................................................................. 78

Configure a Container Instance IAM Role ........................................................................ 78

Define Docker Containers ............................................................................................. 80

Add Content ............................................................................................................... 82

Deploy to Elastic Beanstalk ........................................................................................... 82

Connect to a Container Instance .................................................................................... 83

Inspect the Amazon ECS Container Agent ....................................................................... 85

Applications from Preconfigured Docker Containers ........................................................................... 87

Getting Started with Preconfigured Docker Containers ............................................................... 87

Set Up Your Local Development Environment ................................................................... 87

Develop and Test Locally ............................................................................................... 88

Deploy to Elastic Beanstalk ........................................................................................... 89

Example: Customize and Configure Preconfigured Docker Platforms ............................................ 89

Go Applications Using Preconfigured Docker Containers .................................................................... 90

Getting Started with Go Preconfigured Docker Containers .......................................................... 90

Set Up Your Local Development Environment ................................................................... 90

Develop and Test Locally Using Docker ............................................................................ 91

Deploy to Elastic Beanstalk ........................................................................................... 92

Java Applications Using Eclipse ..................................................................................................... 93

Develop, Test, and Deploy ..................................................................................................... 93

Create Project ............................................................................................................. 94

Test Locally ................................................................................................................ 96

Deploy to AWS Elastic Beanstalk .................................................................................... 98

Debug/View Logs ....................................................................................................... 101

Edit the Application and Redeploy ................................................................................. 101

Deploy to Production .................................................................................................. 102

Importing Existing Environments into Eclipse .......................................................................... 102

Using Custom Environment Properties .................................................................................. 102

Setting Custom Environment Properties with AWS Toolkit for Eclipse .................................. 102

Setting Custom Environment Properties with AWS Management Console ............................ 103

Accessing Custom Environment Properties .................................................................... 104

Using Amazon RDS and MySQL Connector/J ......................................................................... 105

Using a New Amazon RDS DB Instance with Java ........................................................... 105

Using an Existing Amazon RDS DB Instance with Java ..................................................... 107

Troubleshooting Database Connections ......................................................................... 108

Managing Multiple AWS Accounts ......................................................................................... 110

Viewing Events ................................................................................................................. 111

Managing Environments ...................................................................................................... 112

Changing Environment Configuration Settings ................................................................. 112

Environment Types ..................................................................................................... 113

API Version 2010-12-01

Elastic Beanstalk Developer Guide

EC2 Server Instances ................................................................................................. 113

Elastic Load Balancing ................................................................................................ 116

Auto Scaling .............................................................................................................. 118

Notifications .............................................................................................................. 120

Containers ................................................................................................................ 121

Listing and Connecting to Server Instances ............................................................................ 123

................................................................................................................................ 414

Terminating an Environment ................................................................................................. 123

................................................................................................................................ 124

Tools ................................................................................................................................ 124

AWS SDK for Java ..................................................................................................... 124

AWS Toolkit for Eclipse ............................................................................................... 124

Resources ........................................................................................................................ 124

.NET Applications Using Visual Studio ........................................................................................... 125

Get Started ....................................................................................................................... 126

Step 1: Set Up the NerdDinner Application ..................................................................... 126

Step 2: Launch an Amazon RDS DB Instance ................................................................. 127

Step 3: Set Up the NerdDinner Database ....................................................................... 128

Step 4: Deploy to Elastic Beanstalk ............................................................................... 131

Develop, Test, and Deploy ................................................................................................... 134

Create a Project ......................................................................................................... 135

Test Locally ............................................................................................................... 135

Deploy to AWS Elastic Beanstalk ................................................................................. 136

Debug/View Logs ...................................................................................................... 143

Edit the Application and Redeploy ................................................................................. 143

Deploy to Production .................................................................................................. 144

Deploy an Existing Application Version to an Existing Environment ..................................... 149

Customizing and Configuring a .NET Environment ................................................................... 150

Accessing Environment Configuration Settings ................................................................ 151

Using Amazon RDS ........................................................................................................... 152

Using a New Amazon RDS DB Instance with .NET .......................................................... 152

Using an Existing Amazon RDS DB Instance with .NET .................................................... 153

Managing Multiple Accounts ................................................................................................ 154

................................................................................................................................ 154

Monitoring Application Health ............................................................................................... 155

Understanding Environment Health ............................................................................... 155

Viewing Application Health and Environment Status ......................................................... 157

................................................................................................................................ 157

Viewing Events .................................................................................................................. 158

Managing Environments ...................................................................................................... 159

Changing Environment Configurations Settings ............................................................... 159

EC2 Server Instances ................................................................................................. 159

Elastic Load Balancing ................................................................................................ 162

Auto Scaling .............................................................................................................. 165

Notifications .............................................................................................................. 166

Containers ................................................................................................................ 167

Listing and Connecting to Server Instances ............................................................................ 168

................................................................................................................................ 414

Terminating an Environment ................................................................................................. 169

................................................................................................................................ 169

Tools ................................................................................................................................ 170

AWS SDK for .NET ..................................................................................................... 170

AWS Toolkit for Visual Studio ........................................................................................ 170

Deployment Tool ........................................................................................................ 170

Resources ........................................................................................................................ 173

Node.js Applications Using EB CLI and Git ..................................................................................... 174

Develop, Test, and Deploy ................................................................................................... 174

Get Set Up ................................................................................................................ 175

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Develop Locally ......................................................................................................... 175

Test Locally ............................................................................................................... 176

Deploy to AWS Elastic Beanstalk ................................................................................. 176

Debug/View Logs ...................................................................................................... 178

Edit the Application and Redeploy ................................................................................. 178

Deploy to Production .................................................................................................. 179

Deploy an Existing Application Version to an Existing Environment ..................................... 179

Deploying an Express Application ......................................................................................... 179

Step 1: Set Up Your Git Repository ................................................................................ 180

Step 2: Set Up Your Express Development Environment .................................................... 180

Step 3: Configure Elastic Beanstalk ............................................................................... 204

Step 4: View the Application ......................................................................................... 183

Step 5: Update the Application ..................................................................................... 183

Step 6: Clean Up ....................................................................................................... 191

Deploying an Express Application with Clustering .................................................................... 191

Step 1: Set Up Your Git Repository ................................................................................ 192

Step 2: Set Up Your Express Development Environment .................................................... 192

Step 3: Configure Elastic Beanstalk ............................................................................... 204

Step 4: View the Application ......................................................................................... 195

Step 5: Update the Application ..................................................................................... 195

Step 6: Clean Up ....................................................................................................... 202

Deploying a Geddy Application with Clustering ........................................................................ 202

Step 1: Set Up Your Git Repository ................................................................................ 202

Step 2: Set Up Your Geddy Development Environment ...................................................... 203

Step 3: Configure Elastic Beanstalk ............................................................................... 204

Step 5: View the Application ......................................................................................... 205

Step 6: Update the Application ..................................................................................... 206

Step 7: Clean Up ....................................................................................................... 213

Customizing and Configuring a Node.js Environment ............................................................... 213

Accessing Environment Configuration Settings ................................................................ 215

Example: Configuring Nginx and Apache ........................................................................ 215

Using the Console .............................................................................................................. 215

Using Amazon RDS ........................................................................................................... 216

Using a New Amazon RDS DB Instance with Node.js ....................................................... 217

Using an Existing Amazon RDS DB Instance with Node.js ................................................. 218

Tools ................................................................................................................................ 219

AWS SDK for Node.js ................................................................................................. 219

Git Deployment Via Eb ................................................................................................ 219

Resources ........................................................................................................................ 219

PHP Applications Using Eb and Git ............................................................................................... 220

Develop, Test, and Deploy ................................................................................................... 220

Get Set Up ................................................................................................................ 221

Develop Locally ......................................................................................................... 221

Test Locally ............................................................................................................... 222

Deploy to AWS Elastic Beanstalk ................................................................................. 222

Debug/View Logs ...................................................................................................... 224

Edit the Application and Redeploy ................................................................................. 224

Deploy to Production .................................................................................................. 225

Deploy an Existing Application Version to an Existing Environment ..................................... 225

Deploying a Symfony2 Application ........................................................................................ 225

Step 1: Set Up Your Git Repository ................................................................................ 226

Step 2: Set Up Your Symfony2 Development Environment ................................................. 226

Step 3: Configure Elastic Beanstalk ............................................................................... 227

Step 4: View the Application ......................................................................................... 229

Step 5: Update the Application ..................................................................................... 229

Step 6: Clean Up ....................................................................................................... 229

Deploying a CakePHP Application ........................................................................................ 230

Step 1: Set Up Your Git Repository ................................................................................ 230

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Step 2: Set Up Your CakePHP Development Environment ................................................. 230

Step 3: Configure Elastic Beanstalk ............................................................................... 231

Step 4: View the Application ......................................................................................... 233

Step 5: Update the Application ..................................................................................... 233

Step 6: Clean Up ....................................................................................................... 234

Deploying Using the Console ............................................................................................... 235

Customizing and Configuring a PHP Environment .................................................................... 236

Accessing Environment Configuration Settings ................................................................ 237

Using Amazon RDS ........................................................................................................... 237

Using a New Amazon RDS DB Instance with PHP ........................................................... 238

Using an Existing Amazon RDS DB Instance with PHP ..................................................... 239

Tools ................................................................................................................................ 240

AWS SDK for PHP ..................................................................................................... 240

Git Deployment Via Eb ................................................................................................ 241

Resources ........................................................................................................................ 241

Python Applications Using EB CLI and Git ...................................................................................... 242

Deploying a Django Application ............................................................................................ 243

Step 1: Set Up Your Git Repository ................................................................................ 243

Step 2: Set Up Your Python Development Environment ..................................................... 243

Step 3: Configure Elastic Beanstalk ............................................................................... 245

Step 3: View Application .............................................................................................. 246

Step 4: Update Application ........................................................................................... 247

Step 5: Configure the Django Admin Site (Optional) ......................................................... 249

Step 6: Clean Up ....................................................................................................... 251

Deploying a Flask Application ............................................................................................... 252

Step 1: Initialize Your Git Repository .............................................................................. 252

Step 2: Configure Elastic Beanstalk ............................................................................... 252

Step 3: View Application .............................................................................................. 254

Step 4: Update Application ........................................................................................... 254

Step 5: Clean Up ....................................................................................................... 255

Using the Console .............................................................................................................. 256

Customizing and Configuring a Python Container .................................................................... 256

Accessing Environment Variables ................................................................................. 258

Using Amazon RDS ........................................................................................................... 258

Using a New Amazon RDS DB Instance with Python ........................................................ 259

Using an Existing Amazon RDS DB Instance with Python ................................................. 260

Tools ................................................................................................................................ 261

Boto (open source AWS SDK for Python) ....................................................................... 261

Git Deployment Via Eb ................................................................................................ 261

Resources ........................................................................................................................ 261

Ruby Applications Using EB CLI and Git ........................................................................................ 262

Deploying a Rails Application ............................................................................................... 262

Rails Development Environment Setup .......................................................................... 263

Install the EB CLI ....................................................................................................... 264

Set Up Your Git Repository .......................................................................................... 265

Configure the EB CLI .................................................................................................. 265

Deploy the Project ...................................................................................................... 266

Update the Application ................................................................................................ 268

Clean Up ................................................................................................................. 269

Deploying a Sinatra Application ............................................................................................ 270

Step 1: Set Up Your Git Repository ................................................................................ 270

Step 2: Configure Elastic Beanstalk ............................................................................... 270

Step 3: View the Application ......................................................................................... 272

Step 4: Update the Application ..................................................................................... 272

Step 5: Clean Up ....................................................................................................... 273

Customizing and Configuring a Ruby Environment ................................................................... 273

Accessing Environment Variables ................................................................................. 274

Using Amazon RDS ........................................................................................................... 275

API Version 2010-12-01

vii

Elastic Beanstalk Developer Guide

Using a New Amazon RDS DB Instance with Ruby .......................................................... 275

Using an Existing Amazon RDS DB Instance with Ruby .................................................... 276

Tools ................................................................................................................................ 277

AWS SDK for Ruby .................................................................................................... 277

Git Deployment Via EB CLI .......................................................................................... 277

Resources ........................................................................................................................ 277

Managing Applications ................................................................................................................ 278

Creating New Applications ................................................................................................... 279

AWS Management Console ......................................................................................... 279

Command Line Interface (CLI) ...................................................................................... 287

API .......................................................................................................................... 288

Creating New Application Versions ........................................................................................ 292

AWS Management Console ......................................................................................... 421

CLI .......................................................................................................................... 422

API .......................................................................................................................... 422

Creating an Application Source Bundle .................................................................................. 294

Zipping Files in Mac OS X Finder or Windows Explorer ..................................................... 294

Creating a Source Bundle from the Command Line .......................................................... 297

Creating a Source Bundle with Git ................................................................................ 298

Testing Your Source Bundle ......................................................................................... 298

Filtering Applications .......................................................................................................... 299

Launching New Environments .............................................................................................. 299

AWS Management Console ......................................................................................... 299

CLI .......................................................................................................................... 308

API .......................................................................................................................... 309

Deploying Versions to Existing Environments .......................................................................... 313

AWS Management Console ......................................................................................... 427

CLI .......................................................................................................................... 316

API .......................................................................................................................... 317

Deploying Versions with Zero Downtime ................................................................................. 318

AWS Management Console ......................................................................................... 318

CLI .......................................................................................................................... 321

API .......................................................................................................................... 325

Monitoring Application Health ............................................................................................... 327

Health Monitoring ....................................................................................................... 328

Monitoring Your Environment ........................................................................................ 330

Managing Alarms ............................................................................................................... 331

Viewing Events .................................................................................................................. 333

AWS Management Console ......................................................................................... 334

CLI .......................................................................................................................... 334

API .......................................................................................................................... 335

Managing Environments ...................................................................................................... 335

Changing Environment Configuration Settings ................................................................. 336

Environment Tiers ...................................................................................................... 337

Environment Types ..................................................................................................... 345

Changing Environment Type ........................................................................................ 346

Saving Environment Configuration Settings .................................................................... 348

Cloning an Environment .............................................................................................. 350

Amazon EC2 Server Instances ..................................................................................... 352

Elastic Load Balancing ................................................................................................ 358

Auto Scaling .............................................................................................................. 367

Rolling Updates ......................................................................................................... 375

Deploying Versions in Batches ...................................................................................... 379

Canceling Environment and Application Version Updates .................................................. 381

Upgrading the Platform ............................................................................................... 382

Databases ................................................................................................................ 384

Notifications .............................................................................................................. 387

Tagging Environments ................................................................................................ 389

API Version 2010-12-01

viii

Elastic Beanstalk Developer Guide

Environment Configurations ......................................................................................... 389

VPC ........................................................................................................................ 413

Listing and Connecting to Server Instances ............................................................................ 413

................................................................................................................................ 414

Working with Logs .............................................................................................................. 415

Viewing Tail Log Snapshots in the Elastic Beanstalk Console ............................................. 415

Downloading Bundle Logs from the Elastic Beanstalk Console ........................................... 417

Configuring Your Environment to Publish Logs to Amazon S3 ............................................ 419

Deleting Application Versions ............................................................................................... 421

AWS Management Console ......................................................................................... 421

CLI .......................................................................................................................... 422

API .......................................................................................................................... 422

Terminating an Environment ................................................................................................. 423

AWS Management Console ......................................................................................... 423

CLI .......................................................................................................................... 424

API .......................................................................................................................... 424

Customizing Your Environments ............................................................................................ 425

Migrating Your Application from a Legacy Container Type .......................................................... 426

Why are some container types marked legacy? ............................................................... 426

Constructing a Launch Now URL .......................................................................................... 427

URL Parameters ........................................................................................................ 427

Example ................................................................................................................... 429

Customizing and Configuring Environments .................................................................................... 430

Supported Container Types .................................................................................................. 430

Using Configuration Files .................................................................................................... 431

Customizing the Software on EC2 Instances Running Linux ...................................................... 431

Packages ................................................................................................................. 432

Sources ................................................................................................................... 433

Files ........................................................................................................................ 434

Users ....................................................................................................................... 435

Groups ..................................................................................................................... 436

Commands ............................................................................................................... 436

Container_commands ................................................................................................. 437

Services ................................................................................................................... 439

Option_settings ......................................................................................................... 440

Example: Using Custom Amazon CloudWatch Metrics ..................................................... 441

Customizing the Software on EC2 Instances Running Windows ................................................. 447

Packages ................................................................................................................. 448

Sources ................................................................................................................... 449

Files ........................................................................................................................ 449

Commands ............................................................................................................... 450

Container_commands ................................................................................................. 451

Services ................................................................................................................... 452

Option_settings ......................................................................................................... 454

Example: Using Custom Amazon CloudWatch Metrics ..................................................... 455

Customizing Environment Resources .................................................................................... 456

Resources ................................................................................................................ 457

Example Snippets: ElastiCache .................................................................................... 459

Example Snippet: SQS, CloudWatch, and SNS ............................................................... 465

Example: DynamoDB, CloudWatch, and SNS ................................................................. 467

Example Snippets ...................................................................................................... 477

Using Custom Domains .............................................................................................................. 478

Using a Domain Hosted by a Third Party ................................................................................ 478

Using a Domain Hosted by Amazon Route 53 ......................................................................... 479

Configuring HTTPS .................................................................................................................... 482

Step 1: Create a Custom Domain .......................................................................................... 482

Step 2: Create and Upload an SSL Certificate to AWS IAM ....................................................... 483

Install and Configure OpenSSL .................................................................................... 483

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Create a Private Key ................................................................................................... 484

Create a Certificate Signing Request ............................................................................. 484

Submit the CSR to Certificate Authority .......................................................................... 485

Upload the Signed Certificate ....................................................................................... 486

Step 3: Update Your Elastic Beanstalk Environment to Use HTTPS ............................................. 486

SSL on Single Instances ............................................................................................................. 489

Step 1: Create an SSL Certificate and Private Key ................................................................... 489

Step 2: Create an SSL Configuration File ............................................................................... 490

Step 3: Open Port 443 ........................................................................................................ 490

Step 4: Complete the Configuration File for Your Container Type ................................................. 491

SSL on Docker .................................................................................................................. 491

SSL on Java/Apache Tomcat ................................................................................................ 494

SSL on Node.js ................................................................................................................. 496

SSL on PHP ..................................................................................................................... 500

SSL on Python .................................................................................................................. 502

SSL on Ruby ..................................................................................................................... 506

Ruby with Puma ........................................................................................................ 506

Ruby with Passenger .................................................................................................. 509

Troubleshooting ......................................................................................................................... 510

Launch Events .................................................................................................................. 512

HTTP HEAD Request to Your Elastic Beanstalk URL Fails ................................................. 512

CPU Utilization Exceeds 95.00% .................................................................................. 513

Elastic Load Balancer Has Zero Healthy Instances .......................................................... 513

Elastic Load Balancer Cannot Be Found ........................................................................ 513

Instance Fails to Respond to Status Health Check ........................................................... 515

Environment Launch Fails ........................................................................................... 515

Amazon EC2 Instance Launch Fails .............................................................................. 515

Application Does Not Enter the Ready State Within the Timeout Period ............................... 515

Environment Launches but with Issues .......................................................................... 516

Amazon EC2 Instances Fail to Launch within the Wait Period ............................................. 516

Launch and Update Environment Operations Succeeded but with Command Timeouts .......... 517

Docker Containers ............................................................................................................. 518

Dockerfile Syntax Errors .............................................................................................. 518

Dockerrun.aws.json Syntax Errors ................................................................................. 518

No EXPOSE Directive Found in Dockerfile ...................................................................... 519

Invalid EC2 Key Pair and/or S3 Bucket in Dockerrun.aws.json ............................................ 520

Other AWS Services ................................................................................................................... 521

Architectural Overview ........................................................................................................ 521

Amazon CloudFront ............................................................................................................ 522

AWS CloudTrail ................................................................................................................. 522

Amazon CloudWatch .......................................................................................................... 523

Amazon CloudWatch Logs ................................................................................................... 523

Granting IAM Permissions ........................................................................................... 525

Setting Up CloudWatch Logs Integration with Configuration Files ....................................... 526

Troubleshooting CloudWatch Logs Integration ................................................................. 527

DynamoDB ....................................................................................................................... 527

Amazon ElastiCache .......................................................................................................... 527

Amazon RDS .................................................................................................................... 528

Amazon Route 53 .............................................................................................................. 528

Amazon S3 ....................................................................................................................... 531

Amazon VPC .................................................................................................................... 531

What VPC Configurations Do I Need? ............................................................................ 531

Example: Launching a Single-Instance Environment without Any Associated Private Resources

in a VPC ................................................................................................................... 533

Example: Launching a Load-Balancing, Autoscaling Environment with Private Instances in a

VPC ........................................................................................................................ 536

Example: Bastion Hosts .............................................................................................. 542

Example: Amazon RDS ............................................................................................... 550

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Example: Launching a Load-Balancing, Autoscaling Environment with Public Instances in a

VPC ........................................................................................................................ 557

IAM ................................................................................................................................. 561

Granting Permissions to IAM Users ............................................................................... 561

Granting Permissions to Users and Services Using IAM Roles ........................................... 562

Using Policies to Control Access to Resources ................................................................ 563

Using Policy Templates to Control Access to All Resources ............................................... 563

Creating Policies to Control Access to Specific Resources ................................................ 564

Using IAM Roles ........................................................................................................ 568

Amazon Resource Name (ARN) Format ......................................................................... 579

Resources and Conditions for Actions ........................................................................... 581

Example Policies Based on Policy Templates ................................................................. 604

Example Policies Based on Resource Permissions ......................................................... 607

IAM Roles for Environment Tiers ................................................................................... 617

Tools ........................................................................................................................................ 620

EB and Eb Command Line Interfaces .................................................................................... 620

EB CLI 3.x ................................................................................................................ 621

Eb CLI 2.6.x .............................................................................................................. 672

AWS Command Line Interface .............................................................................................. 698

Migrating to the AWS CLI ............................................................................................ 699

API Command Line Interface ............................................................................................... 704

Getting Set Up ........................................................................................................... 704

Common Options ....................................................................................................... 706

Option Values ............................................................................................................ 707

Operations ................................................................................................................ 736

AWS DevTools ................................................................................................................... 785

Getting Set Up ........................................................................................................... 785

Develop, Test, and Deploy ........................................................................................... 788

Resources ................................................................................................................................ 794

Sample Applications ........................................................................................................... 794

Document History ...................................................................................................................... 796

Appendix .................................................................................................................................. 802

Customizing AWS Resources ............................................................................................... 802

AWS Resource Types ................................................................................................. 802

Resource Property Types ............................................................................................ 810

Intrinsic Functions ...................................................................................................... 812

Updating Stacks ........................................................................................................ 814

Using Amazon RDS ........................................................................................................... 815

................................................................................................................................ 815

Using Amazon RDS and MySQL Connector/J (Legacy Container Types) ..................................... 816

................................................................................................................................ 816

Using Custom AMIs ............................................................................................................ 817

................................................................................................................................ 817

API Version 2010-12-01

Elastic Beanstalk Developer Guide

What Is Elastic Beanstalk and Why

Do I Need It?

Amazon Web Services (AWS) comprises dozens of services, each of which exposes an area of

functionality.While the variety of services offers flexibility for how you want to manage your AWS

infrastructure, it can be challenging to figure out which services to use and how to provision them.

With Elastic Beanstalk, you can quickly deploy and manage applications in the AWS cloud without worrying

about the infrastructure that runs those applications. AWS Elastic Beanstalk reduces management

complexity without restricting choice or control.You simply upload your application, and Elastic Beanstalk

automatically handles the details of capacity provisioning, load balancing, scaling, and application health

monitoring. Elastic Beanstalk uses highly reliable and scalable services that are available in the AWS

Free Usage Tier such as:

• Amazon Elastic Compute Cloud

• Amazon Simple Storage Service

• Amazon Simple Notification Service

• Amazon CloudWatch

• Elastic Load Balancing

• Auto Scaling

• Amazon RDS

• Amazon DynamoDB

• Amazon CloudFront

• Amazon ElastiCache

To learn more about the AWS Free Usage Tier, and how to deploy a sample web application in it using

AWS Elastic Beanstalk, go to Getting Started with AWS: Deploying a Web Application.

You can also perform most deployment tasks, such as changing the size of your fleet of Amazon EC2

instances or monitoring your application, directly from the Elastic Beanstalk web interface.

To use Elastic Beanstalk, you create an application, upload an application version in the form of an

application source bundle (for example, a Java .war file) to Elastic Beanstalk, and then provide some

information about the application. Elastic Beanstalk automatically launches an environment and creates

API Version 2010-12-01

Elastic Beanstalk Developer Guide

and configures the AWS resources needed to run your code. After your environment is launched, you

can then manage your environment and deploy new application versions.The following diagram illustrates

the workflow of Elastic Beanstalk.

After you create and deploy your application, information about the application—including metrics, events,

and environment status—is available through the AWS Management Console, APIs, or Command Line

Interfaces, including the unified AWS CLI. For step-by-step instructions on how to create, deploy, and

manage your application using the AWS Management Console, go to Getting Started Using Elastic

Beanstalk (p. 4). To learn more about an Elastic Beanstalk application and its components, see Elastic

Beanstalk Components (p. 15).

Elastic Beanstalk provides developers and systems administrators an easy, fast way to deploy and

manage their applications without having to worry about AWS infrastructure. If you already know the AWS

resources you want to use and how they work, you might prefer AWS CloudFormation to create your

AWS resources by creating a template.You can then use this template to launch new AWS resources

in the exact same way without having to recustomize your AWS resources. Once your resources are

deployed, you can modify and update the AWS resources in a controlled and predictable way, providing

the same sort of version control over your AWS infrastructure that you exercise over your software. For

more information about AWS CloudFormation, go to AWS CloudFormation Getting Started Guide.

Storage

Elastic Beanstalk does not restrict your choice of persistent storage and database service options. For

more information on AWS storage options, go to Storage Options in the AWS Cloud.

Pricing

There is no additional charge for Elastic Beanstalk.You pay only for the underlying AWS resources that

your application consumes. For details about pricing, see the Elastic Beanstalk service detail page.

Community

Customers have built a wide variety of products, services, and applications on top of AWS. Whether you

are searching for ideas about what to build, looking for examples, or just want to explore, you can find

many solutions at the AWS Customer App Catalog.You can browse by audience, services, and technology.

We also invite you to share applications you build with the community. Developer resources produced

by the AWS community are at http://aws.amazon.com/resources/.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Storage

Where to Go Next

This guide contains conceptual information about the Elastic Beanstalk web service, as well as information

about how to use the service to deploy web applications. Separate sections describe how to use the AWS

Management console, command line interface (CLI) tools, and API to deploy and manage your Elastic

Beanstalk environments.This guide also documents how Elastic Beanstalk is integrated with other services

provided by Amazon Web Services.

We recommend that you first read Getting Started Using Elastic Beanstalk (p. 4) to learn how to start

using Elastic Beanstalk. Getting Started steps you through creating, viewing, and updating your Elastic

Beanstalk application, as well as editing and terminating your Elastic Beanstalk environment. Getting

Started also describes different ways you can access Elastic Beanstalk. We also recommend that you

familiarize yourself with Elastic Beanstalk concepts and terminology by reading How Does Elastic Beanstalk

Work? (p. 15).

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Where to Go Next

Getting Started Using Elastic

Beanstalk

Topics

• Walkthrough (p. 4)

• Accessing Elastic Beanstalk (p. 11)

• Where to Go Next (p. 14)

Getting started with Elastic Beanstalk is simple, and the AWS Management Console makes it easy for

you to create, edit, and manage your Docker, Go, Java, PHP, .NET, Node.js, Python, and Ruby applications

in a matter of minutes.The following walkthrough steps you through how to use the console to get started.

You can also access Elastic Beanstalk using the AWS Toolkit for Eclipse, AWS Toolkit for Microsoft Visual

Studio, AWS SDKs, APIs, and CLIs; for more information about these tools, see AWS Developer Tools.

The remainder of this section provides information about each of these and where to go next.

Walkthrough

The following tasks will help you get started with Elastic Beanstalk to create, view, deploy, and update

your application as well as edit and terminate your environment.You'll use the AWS Management Console,

a point-and-click web-based interface, to complete these tasks.

Step 1: Sign up for the Service

If you're not already an AWS customer, you'll need to sign up. Signing up allows you to access Elastic

Beanstalk and other AWS services that you will need, such as Amazon Elastic Compute Cloud (Amazon

EC2), Amazon Simple Storage Service (Amazon S3), and Amazon Simple Notification Service (Amazon

SNS).

To sign up for an AWS account

1. Open the Elastic Beanstalk console at https://console.aws.amazon.com/elasticbeanstalk/.

2. Follow the on-screen instructions.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Walkthrough

Note

If you have never registered for Amazon EC2, part of the sign-up procedure for Elastic Beanstalk

will include receiving an automated telephone call and entering a PIN using the telephone keypad.

Step 2: Create an Application

Next, you will create and deploy a sample application. For this step, you use a sample application that is

already prepared. If any Elastic Beanstalk applications already exist in the region in which you want to

create and deploy an application, you must follow different procedures to create a new application. For

more information, see Creating New Applications (p. 279).

Important

Elastic Beanstalk is free, but the AWS resources that it provides will be live (and not running in

a sandbox).You will incur the standard usage fees for these resources until you terminate them

in the last task in this tutorial. The total charges will be minimal (typically less than a dollar). For

information on how you might minimize any charges, go to http://aws.amazon.com/free/.

To create a sample application

1. Open the Elastic Beanstalk console at https://console.aws.amazon.com/elasticbeanstalk/.

2. Select a platform and then click Launch Now.

To run a sample application on AWS resources, Elastic Beanstalk takes the following actions, which can

take several minutes to complete:

• Creates an Elastic Beanstalk application named My First Elastic Beanstalk Application.

• Launches an environment named Default-Environment that provisions the AWS resources to host

the sample application.

• Creates a new application version named Sample Application, which refers to the default Elastic

Beanstalk sample application file.

• Deploys the Sample Application application into the Default-Environment.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Step 2: Create an Application

Step 3:View Information About Your Environment

After you create the Elastic Beanstalk application, you can view information about the application you

deployed and its provisioned resources by going to the environment dashboard in the AWS Management

Console.The dashboard shows the health of your application's environment, the running version, and

the environment configuration.

While Elastic Beanstalk creates your AWS resources and launches your application, the environment will

be in a Launching (gray) state. Status messages about launch events are displayed in the environment's

dashboard.

To see the environment dashboard for the My First Elastic Beanstalk Application application

1. Open the Elastic Beanstalk console at https://console.aws.amazon.com/elasticbeanstalk/.

2. From the Elastic Beanstalk applications page, click Default-Environment in the My First Elastic

Beanstalk Application application.

From the dashboard you can view the status of the environment, the running application version, the

platform, and a list of recent events.

Note

If the environment health is gray, the environment is still in the process of being launched.

You can also view additional details about the environment by going to other pages from the dashboard:

• The Configuration page shows the resources provisioned for this environment, such as Amazon EC2

instances that host your application.This page also lets you configure some of the provisioned resources.

• The Logs page lets you view a snapshot of the last 100 lines of logs or review all logs for all your

servers.

• The Monitoring page shows the statistics for the environment, such as average latency and CPU

utilization.This page also lets you create alarms for the metrics that you are monitoring.

• The Alarms page shows the CloudWatch alarms you've created for this environment.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Step 3:View Information About Your Environment

• The Events page shows any informational or error messages from services that this environment is

using.

• The Tags page shows the metadata that you assigned in the form of tags to this environment. Each

tag is represented on the page as a key-value pair. The page includes tags that Elastic Beanstalk

automatically creates for the environment name and environment ID. For more information about tags,

see Tagging Your Environments (p. 389).

Step 4: Deploy New Version

You can update your deployed application, even while it is part of a running environment. For a Java

application, you can also use the AWS Toolkit for Eclipse to update your deployed application; for

instructions, see Edit the Application and Redeploy (p. 101). For a PHP application, it is easy to update

your application using a Git deployment via eb; for instructions, see Deploying Elastic Beanstalk

Applications in PHP (p. 220). For a .NET application, you can use the AWS Toolkit for Visual Studio to

update your deployed application; for instructions, see Edit the Application and Redeploy (p. 143).

The application version you are running now is labeled Sample Application.

To update your application version

1. Download one of the following sample applications that match the configuration for your environment:

• Docker–Go to https://s3.amazonaws.com/elasticbeanstalk-samples-us-east-1/docker-sample-v3.zip

and save the file as docker-sample-v3.zip.

• Preconfigured Docker (Glassfish)–Go to https://s3.amazonaws.com/

elasticbeanstalk-samples-us-east-1/glassfish-sample.war and save the file as

glassfish-sample.war.

• Preconfigured Docker (Python 3.x)–Go to http://

elasticbeanstalk-samples-us-east-1.s3.amazonaws.com/python3-sample.zip and save the file as

python3-sample.zip.

• Preconfigured Docker (Go)–Go to http://elasticbeanstalk-samples-us-east-1.s3.amazonaws.com/

golang-sample.zip and save the file as golang-sample.zip.

• Java–Go to https://elasticbeanstalk-samples-us-east-1.s3.amazonaws.com/

elasticbeanstalk-sampleapp.war and save the file as elasticbeanstalk-sampleapp.war.

• .NET–Go to https://elasticbeanstalk-samples-us-east-1.s3.amazonaws.com/FirstSample.zip and

save the file as FirstSample.zip.

• Node.js–Go to http://s3.amazonaws.com/elasticbeanstalk-samples-us-east-1/nodejs-sample.zip

and save the file as nodejs-sample.zip.

• PHP–Go to http://s3.amazonaws.com/elasticbeanstalk-samples-us-east-1/php-newsample-app.zip

and save the file as php-newsample-app.zip.

• Python–Go to http://s3.amazonaws.com/elasticbeanstalk-samples-us-east-1/basicapp.zip and

save the file as basicapp.zip.

• Ruby (Passenger Standalone)–Go to http://s3.amazonaws.com/

elasticbeanstalk-samples-us-east-1/ruby-sample.zip and save the file as ruby-sample.zip.

• Ruby (Puma)–Go to http://s3.amazonaws.com/elasticbeanstalk-samples-us-east-1/

ruby2PumaSampleApp.zip and save the file as ruby2PumaSampleApp.zip.

2. Open the Elastic Beanstalk console at https://console.aws.amazon.com/elasticbeanstalk/.

3. From the Elastic Beanstalk applications page, click My First Elastic Beanstalk Application and

then click Default-Environment.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Step 4: Deploy New Version

4. In the Overview section, click Upload and Deploy and then enter details about the application

version.

• Use Upload application to locate and specify the application version (WAR or ZIP file) that you

want to upload.

• For Version label, enter a name for the application version that you are uploading, such as Sample

Application Second Version.

5. Click Deploy.

Elastic Beanstalk now deploys your file to your Amazon EC2 instances.You can view the status of your

deployment on the environment's dashboard.The Environment Health status turns gray while the

application version is updated.When the deployment is complete, Elastic Beanstalk performs an application

health check.The status returns to green when the application responds to the health check.The

environment dashboard will show the new Running Version as Sample Application Second Version

(or whatever you provided as the Version label.

Your new application version is also uploaded and added to the table of application versions.To view

the table of application versions, click My First Elastic Beanstalk Application and then click Application

Versions.

Step 5: Change Configuration

You can customize your environment to better suit your application. For example, if you have a

compute-intensive application, you can change the type of Amazon EC2 instance that is running your

application.

Some configuration changes are simple and happen quickly. Some changes require Elastic Beanstalk

to delete and recreate AWS resources, which can take several minutes. Elastic Beanstalk will warn you

about possible application downtime when changing configuration settings.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Step 5: Change Configuration

In this task, you change the minimum instance settings for your Auto Scaling group from one to two and

then verify that the change occurred. After the new instance gets created, it will become associated with

your load balancer.

To change your environment configuration

1. Go back to the environment dashboard by clicking My First Elastic Beanstalk Application and

then Default-Environment.

2. In the navigation pane, click Configuration.

In the Scaling settings, click the gear icon ( ).

4. In the Auto Scaling section, change Minimum Instance Count from 1 to 2.This increases the

minimum number of Auto Scaling instances deployed in Amazon EC2.

5. At the bottom of the page, click Save.

The environment update might take a few minutes. When the environment is ready, you can go to the

next task to verify your changes.

To verify changes to load balancers

1. In the navigation pane, click Events.

You will see the event Successfully deployed new configuration to environment in the events

list.This confirms that the Auto Scaling minimum instance count has been set to 2. A second instance

is launched automatically.

2. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

3. In the navigation pane, under NETWORK & SECURITY, click Load Balancers.

4. Repeat the next two steps until you identify the load balancer with the desired instance name.

5. Click a load balancer in the list of load balancers.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Step 5: Change Configuration

6. Click the Instances tab in the Load Balancer: <load balancer name> pane, and then look at the

Name in the Instances table.

The information shows that two instances are associated with this load balancer, corresponding to

the increase in Auto Scaling instances.

Step 6: Clean Up

Congratulations! You have successfully deployed a sample application to the cloud, uploaded a new

version, and modified its configuration to add a second Auto Scaling instance.To make sure you are not

charged for any services you don't need, delete any unwanted applications and environments from Elastic

Beanstalk and AWS services.

To completely delete the application

1. Delete all application versions.

a. Open the Elastic Beanstalk console at https://console.aws.amazon.com/elasticbeanstalk/.

b. From the Elastic Beanstalk applications page, click Default-Environment in the My First Elastic

Beanstalk Application application.

c. Click Upload and Deploy.

d. When prompted for an application, click Application Versions page.

e. On the Application Versions page, select all application versions that you want to delete, and

then click Delete.

f. Confirm the versions that you are deleting, and then click Delete.

g. Click Done.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Step 6: Clean Up

2. Terminate the environment.

a. Go back to the environment dashboard by clicking My First Elastic Beanstalk Application and

then Default-Environment.

b. Click Actions and then click Terminate Environment.

c. Confirm that you are terminating Default-Environment and then click Terminate.

3. Delete the My First Elastic Beanstalk Application Elastic Beanstalk application.

a. Click Elastic Beanstalk at the upper left to return to the main dashboard.

b. From the Elastic Beanstalk applications page, click Actions for the My First Elastic Beanstalk

Application application and then click Delete Application.

c. Confirm that you want to delete this Elastic Beanstalk application by clicking Delete.

Accessing Elastic Beanstalk

Topics

• AWS Management Console (p. 12)

• Git Deployment Via Eb (p. 12)

• AWS SDK for Java (p. 12)

• AWS Toolkit for Eclipse (p. 12)

• AWS SDK for .NET (p. 13)

• AWS Toolkit for Visual Studio (p. 13)

• AWS SDK for Node.js (p. 13)

• AWS SDK for PHP (p. 13)

• Boto (AWS SDK for Python) (p. 13)

• AWS SDK for Ruby (p. 14)

• Elastic Beanstalk API (p. 14)

• Endpoints (p. 14)

You can create an application using one of several different Elastic Beanstalk interfaces: the Elastic

Beanstalk console in the AWS Management Console, Git deployment using AWS DevTools, the Elastic

Beanstalk command line interface, the AWS Toolkits for Eclipse and Visual Studio, or programmatically

through the AWS SDKs for Java, PHP, .NET, Node.js, Python, Ruby, or the Elastic Beanstalk web service

API.

The simplest and quickest method for creating an application is to use the Elastic Beanstalk console.

This does not require any additional software or tools.The console is a web browser interface that you

can use to create and manage your Elastic Beanstalk applications.

The following sections contain overviews of each of the available Elastic Beanstalk interfaces. In order

to use the Elastic Beanstalk features, you need to have an AWS account and be signed up for Elastic

Beanstalk. For instructions on how to sign up for Elastic Beanstalk, see Step 1: Sign up for the

Service (p. 4).

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Accessing Elastic Beanstalk

AWS Management Console

The AWS Management Console enables you to manage applications through Elastic Beanstalk from a

single web browser interface.The console provides access to all of your deployed applications and gives

you the ability to manage and monitor your applications and environments. From the console you can:

• Create and delete applications

• Add and delete application versions

• Create and delete environments

• Identify the running version within an environment

• View operational metrics

• View application and environment logs

The AWS Management Console is available at http://console.aws.amazon.com/elasticbeanstalk.

For more information about getting started with Elastic Beanstalk using the AWS Management Console,

go to the Managing and Configuring Applications and Environments Using the Console, CLI, and

APIs (p. 278).

Git Deployment Via Eb

Eb is an updated command line interface for AWS Elastic Beanstalk that enables you to deploy applications

quickly and more easily. To learn how to get started using eb, see Getting Started with Eb (p. 672). For

an example of how to use eb for PHP, see Deploying Elastic Beanstalk Applications in PHP (p. 220). For

an example of how to use eb for Python, see Deploying Elastic Beanstalk Applications in Python Using

EB CLI and Git (p. 242).

For a complete CLI reference for more advanced scenarios, see Operations (p.736), and see Getting Set

Up (p. 704) for instructions on how to get set up.

AWS SDK for Java

The AWS SDK for Java provides a Java API you can use to build applications that use AWS infrastructure

services.With the AWS SDK for Java, you can get started in minutes with a single, downloadable package

that includes the AWS Java library, code samples, and documentation.

The AWS SDK for Java requires J2SE Development Kit 5.0 or later.You can download the latest Java

software from http://developers.sun.com/downloads/.The SDK also requires Apache Commons (Codec,

HTTPClient, and Logging), and Saxon-HE third-party packages, which are included in the third-party

directory of the SDK.

For more information on using the AWS SDK for Java, go to the AWS SDK for Java.

AWS Toolkit for Eclipse

With the AWS Toolkit for Eclipse plug-in, you can create new AWS Java web projects that are preconfigured

with the AWS SDK for Java, and then deploy the web applications to Elastic Beanstalk. The Elastic

Beanstalk plug-in builds on top of the Eclipse Web Tools Platform (WTP). The toolkit provides a Travel

Log sample web application template that demonstrates the use of Amazon S3 and Amazon SNS.

To ensure you have all the WTP dependencies, we recommend that you start with the Java EE distribution

of Eclipse, which you can download from http://eclipse.org/downloads/.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

AWS Management Console

For more information on using the Elastic Beanstalk plug-in for Eclipse, go to the AWS Toolkit for Eclipse

web page.To get started creating your Elastic Beanstalk application using Eclipse, see Creating and

Deploying Elastic Beanstalk Applications in Java Using AWS Toolkit for Eclipse (p. 93).

AWS SDK for .NET

The AWS SDK for .NET enables you to build applications that use AWS infrastructure services.With the

AWS SDK for .NET, you can get started in minutes with a single, downloadable package that includes

the AWS .NET library, code samples, and documentation.

The AWS SDK for .NET requires .NET Framework 2.0 or later. It will work with any of the following Visual

Studio editions:

• Microsoft Visual Studio Professional Edition 2010 and 2012 (recommended)

• Microsoft Visual C# 2008 Express Edition

• Microsoft Visual Web Developer 2008 Express Edition

For more information on using the AWS SDK for .NET, go to the AWS SDK for .NET web page.

AWS Toolkit for Visual Studio

With the AWS Toolkit for Visual Studio plug-in, you can deploy an existing .NET application to Elastic

Beanstalk.You can also create new projects using the AWS templates that are preconfigured with the

AWS SDK for .NET. For prerequisite and installation information, go to AWS Toolkit for Visual Studio. To

get started creating your Elastic Beanstalk application using Visual Studio, see Creating and Deploying

Elastic Beanstalk Applications in .NET Using AWS Toolkit for Visual Studio (p. 125).

AWS SDK for Node.js

The AWS SDK for Node.js enables you to build applications on top of AWS infrastructure services. With

the AWS SDK for Node.js, you can get started in minutes with a single, downloadable package that

includes the AWS Node.js library, code samples, and documentation.

For more information on using the AWS SDK for Node.js, go to the AWS SDK for Node.js (Developer

Preview) web page.

AWS SDK for PHP

The AWS SDK for PHP enables you to build applications on top of AWS infrastructure services.With the

AWS SDK for PHP, you can get started in minutes with a single, downloadable package that includes

the AWS PHP library, code samples, and documentation.

The AWS SDK for PHP requires PHP 5.2 or later.

For more information on using the AWS SDK for PHP, go to the AWS SDK for PHP web page.

Boto (AWS SDK for Python)

With Boto, you can get started in minutes with a single, downloadable package complete with the AWS

Python library, code samples, and documentation.You can build Python applications on top of APIs that

take the complexity out of coding directly against web services interfaces.The all-in-one library provides

Python developer-friendly APIs that hide much of the lower-level tasks associated with programming for

the AWS cloud, including authentication, request retries, and error handling. Practical examples are

API Version 2010-12-01

Elastic Beanstalk Developer Guide

AWS SDK for .NET

provided in Python for how to use the libraries to build applications. For information about Boto, sample

code, documentation, tools, and additional resources, go to http://aws.amazon.com/python/.

AWS SDK for Ruby

You can get started in minutes with a single, downloadable package complete with the AWS Ruby library,

code samples, and documentation.You can build Ruby applications on top of APIs that take the complexity

out of coding directly against web services interfaces.The all-in-one library provides Ruby developer-friendly

APIs that hide much of the lower-level tasks associated with programming for the AWS cloud, including

authentication, request retries, and error handling. Practical examples are provided in Ruby for how to

use the libraries to build applications. For information about the SDK, sample code, documentation, tools,

and additional resources, go to http://aws.amazon.com/ruby/.

Elastic Beanstalk API

Elastic Beanstalk provides a comprehensive API that enables you to programmatically access Elastic

Beanstalk functionality. For more information, go to the Elastic Beanstalk API Reference.

Endpoints

For information about this product's regions and endpoints, go to Regions and Endpoints in the Amazon

Web Services General Reference.

Where to Go Next

Now that you have learned about Elastic Beanstalk and how to access it, we recommend that you read

How Does Elastic Beanstalk Work? (p. 15) This topic provides information about the Elastic Beanstalk

components, the architecture, and important design considerations for your Elastic Beanstalk application.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

AWS SDK for Ruby

How Does Elastic Beanstalk Work?

Topics

• Elastic Beanstalk Components (p. 15)

• Architectural Overview (p. 16)

• Supported Platforms (p. 19)

• Design Considerations (p. 58)

• Where to Go Next (p. 60)

Now that you have a better understanding of what Elastic Beanstalk is, let's take a peek under the hood

and see how Elastic Beanstalk works.The following sections discuss the Elastic Beanstalk components,

the architecture, and important design considerations for your Elastic Beanstalk application.

Elastic Beanstalk Components

The components that comprise Elastic Beanstalk work together to enable you to easily deploy and manage

your application in the cloud.This section discusses those components.

Application

An Elastic Beanstalk application is a logical collection of Elastic Beanstalk components, including

environments, versions, and environment configurations. In Elastic Beanstalk an application is conceptually

similar to a folder.

Application Version

In Elastic Beanstalk, an application version refers to a specific, labeled iteration of deployable code for a

web application. An application version points to an Amazon Simple Storage Service (Amazon S3) object

that contains the deployable code such as a Java WAR file. An application version is part of an application.

Applications can have many versions and each application version is unique. In a running environment,

you can deploy any application version you already uploaded to the application or you can upload and

immediately deploy a new application version.You might upload multiple application versions to test

differences between one version of your web application and another.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Components

Environment

An environment is a version that is deployed onto AWS resources. Each environment runs only a single

application version at a time, however you can run the same version or different versions in many

environments at the same time. When you create an environment, Elastic Beanstalk provisions the

resources needed to run the application version you specified. For more information about the environment

and the resources that are created, see Architectural Overview (p. 16).

Environment Configuration

An environment configuration identifies a collection of parameters and settings that define how an

environment and its associated resources behave. When you update an environment’s configuration

settings, Elastic Beanstalk automatically applies the changes to existing resources or deletes and deploys

new resources (depending on the type of change).

Configuration Template

A configuration template is a starting point for creating unique environment configurations. Configuration

templates can be created or modified only by using the Elastic Beanstalk command line utilities or APIs.

Architectural Overview

When you launch an Elastic Beanstalk environment, you choose an environment tier, platform, and

environment type.The environment tier that you choose determines whether Elastic Beanstalk provisions

resources to support a web application that handles HTTP(S) requests or a web application that handles

background-processing tasks. An environment tier whose web application processes web requests is

known as a web server tier. An environment tier whose web application runs background jobs is known

as a worker tier.This topic describes the components, resources, and architecture for each type of

environment tier.

Note

One environment cannot support two different environment tiers because each requires its own

set of resources; a worker environment tier and a web server environment tier each require an

Auto Scaling group, but Elastic Beanstalk supports only one Auto Scaling group per environment.

Web Server Environment Tiers

This following diagram illustrates an example Elastic Beanstalk architecture for a web server environment

tier and shows how the components in that type of environment tier work together. The remainder of this

section discusses all the components in more detail.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Environment

The environment is the heart of the application. In the diagram, the environment is delineated by the

broken yellow line.When you create an environment, Elastic Beanstalk provisions the resources required

to run your application. AWS resources created for an environment include one elastic load balancer

(ELB in the diagram), an Auto Scaling group, and one or more Amazon EC2 instances.

Every environment has a CNAME (URL) that points to a load balancer.The environment has a URL such

as MyApp.elasticbeanstalk.com. This URL is aliased in Amazon Route 53 to an Elastic Load Balancing

URL—something like abcdef-123456.us-west-2.elb.amazonaws.com—by using a CNAME record.Amazon

Route 53 is a highly available and scalable Domain Name System (DNS) web service. It provides secure

and reliable routing to your infrastructure.Your domain name that you registered with your DNS provider

will forward requests to the CNAME.The load balancer sits in front of the Amazon EC2 instances, which

are part of an Auto Scaling group. (The Auto Scaling group is delineated in the diagram by a broken black

line.) Auto Scaling automatically starts additional Amazon EC2 instances to accommodate increasing

load on your application. If the load on your application decreases, Auto Scaling stops instances, but

always leaves at least one instance running. For information about how to map your root domain to your

Elastic Load Balancer, see Using Elastic Beanstalk with Amazon Route 53 to Map Your Domain to Your

Load Balancer (p. 528).

The software stack running on the Amazon EC2 instances is dependent on the container type. A container

type defines the infrastructure topology and software stack to be used for that environment. For example,

an Elastic Beanstalk environment with an Apache Tomcat container uses the Amazon Linux operating

system, Apache web server, and Apache Tomcat software. For a list of supported container types, see

Supported Platforms (p. 19). Each Amazon EC2 server instance that runs your application uses one of

these container types. In addition, a software component called the host manager (HM) runs on each

Amazon EC2 server instance. (In the diagram, the HM is an orange circle in each EC2 instance.) The

host manager is responsible for:

• Deploying the application

• Aggregating events and metrics for retrieval via the console, the API, or the command line

• Generating instance-level events

• Monitoring the application log files for critical errors

• Monitoring the application server

• Patching instance components

• Rotating your application's log files and publishing them to Amazon S3

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Web Server Environment Tiers

The host manager reports metrics, errors and events, and server instance status, which are available via

the AWS Management Console, APIs, and CLIs.

The Amazon EC2 instances shown in the diagram are part of one security group. A security group defines

the firewall rules for your instances. By default, Elastic Beanstalk defines a security group, which allows

everyone to connect using port 80 (HTTP).You can define more than one security group. For instance,

you can define a security group for your database server. For more information about Amazon EC2

security groups and how to configure them for your Elastic Beanstalk application, see the Amazon EC2

Security Groups (p. 354).

Worker Environment Tiers

AWS resources created for a worker environment tier include an Auto Scaling group, one or more Amazon

EC2 instances, and an IAM role. For the worker environment tier, Elastic Beanstalk also creates and

provisions an Amazon SQS queue if you don’t already have one.When you launch a worker environment

tier, Elastic Beanstalk installs the necessary support files for your programming language of choice and

a daemon on each EC2 instance in the Auto Scaling group.The daemon is responsible for pulling requests

from an Amazon SQS queue and then sending the data to the web application running in the worker

environment tier that will process those messages. If you have multiple instances in your worker

environment tier, each instance has its own daemon, but they all read from the same Amazon SQS queue.

The following diagram shows the different components and their interactions across environments and

AWS services.

Amazon CloudWatch is used for alarms and health monitoring. For more information, go to Monitoring

Application Health (p. 327).

For details about how the worker environment tier works, see How the Worker Environment Tier

Works (p. 337).

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Worker Environment Tiers

Supported Platforms

Elastic Beanstalk web server environment tiers support applications developed in Java, PHP, .NET,

Node.js, Python, and Ruby as well as different container types for each language. Elastic Beanstalk

worker environment tiers support applications developed in Node.js, PHP, Python, Ruby, and Java.

Furthermore, for worker environment tiers, only Amazon Linux AMIs are supported.

Elastic Beanstalk provisions the resources needed to run your application including one or more Amazon

EC2 instances.The software stack running on the Amazon EC2 instances depends on the container

type. A container type defines the infrastructure topology and software framework to be used for that

environment. For example, an Elastic Beanstalk environment with an Apache Tomcat container uses the

Amazon Linux operating system, Apache web server, and Apache Tomcat software. In a container name,

the version number refers to the solution stack and not the Amazon Linux operating system version.

• Docker (p. 19)

• Docker - Preconfigured (p. 22)

• Java (p. 27)

• Windows and .NET (p. 32)

• Node.js (p. 33)

• PHP (p. 41)

• Python (p. 46)

• Ruby (p. 50)

Docker

You can use Docker containers to deploy applications to Elastic Beanstalk.They are included in the list

of predefined configurations (or solution stacks) that you can choose when you create an environment.

Elastic Beanstalk supports the following container types:

Docker Container Types

Docker VersionAMIName

1.5.02014.0964bit Amazon Linux 2014.09 v1.2.1 running

Docker 1.5.0

1.3.32014.0964bit Amazon Linux 2014.09 v1.2.0 running

Multi-container Docker 1.3.3 (Generic)

Elastic Beanstalk supports the following container types for environments created with Docker containers

between February 17, 2015 and March 23, 2015:

Docker Container Types

Docker VersionAMIName

1.3.32014.0964bit Amazon Linux 2014.09 v1.2.0 running

Docker 1.3.3

Elastic Beanstalk supports the following container types for environments created with Docker containers

between January 28, 2015 and February 16, 2015:

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Supported Platforms

Docker Container Types

Docker VersionAMIName

1.3.32014.0964bit Amazon Linux 2014.09

v1.1.0 running

Docker 1.3.3

Elastic Beanstalk supports the following container types for environments created with Docker containers

between December 13, 2014 and January 27, 2015:

Docker Container Types

Docker VersionAMIName

1.3.32014.0964bit Amazon Linux 2014.09

v1.0.11 running

Docker 1.3.3

Elastic Beanstalk supports the following container types for environments created with Docker containers

between November 26, 2014 and December 12, 2014:

Docker Container Types

Docker VersionAMIName

1.3.22014.0964bit Amazon Linux 2014.09 v1.0.10 running

Docker 1.3.2

Elastic Beanstalk supports the following container types for environments created with Docker containers

between October 16, 2014 and November 25, 2014:

Docker Container Types

Docker VersionAMIName

1.2.02014.0964bit Amazon Linux 2014.09 v1.0.9

running

Docker 1.2.0

1.0.02014.0364bit Amazon Linux 2014.03 v1.0.9

running

Docker 1.0.0

Elastic Beanstalk supports the following container types for environments created with Docker containers

between October 9, 2014 and October 15, 2014:

Docker Container Types

Docker VersionAMIName

1.2.02014.0964bit Amazon Linux 2014.09 v1.0.8 running

Docker 1.2.0

Elastic Beanstalk supports the following container types for environments created with Docker containers

between September 24, 2014 and October 8, 2014:

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Docker

Docker Container Types

Docker VersionAMIName

1.0.02014.0364bit Amazon Linux 2014.03 v1.0.7

running

Docker 1.0.0

Elastic Beanstalk supports the following container types for environments created with Docker containers

between June 30, 2014 and September 23, 2014:

Docker Container Types

Docker VersionAMIName

1.0.02014.0364bit Amazon Linux 2014.03 v1.0.1 running

Docker 1.0.0

Elastic Beanstalk supports the following container types for environments created with Docker containers

between June 16, 2014 and June 29, 2014:

Docker Container Types

Docker VersionAMIName

1.0.02014.0364bit Amazon Linux 2014.03 v1.0.0 running

Docker 1.0.0

Elastic Beanstalk supports the following container types for environments created with Docker containers

between June 5, 2014 and June 15, 2014:

Docker Container Types

Docker VersionAMIName

0.9.02014.0364bit Amazon Linux 2014.03 v1.0.5

running

Docker 0.9.0

Elastic Beanstalk supports the following container types for environments created with Docker containers

between May 5, 2014 and June 4, 2014:

Docker Container Types

Docker VersionAMIName

0.9.02014.0364bit Amazon Linux 2014.03 v1.0.4 running

Docker 0.9.0

Elastic Beanstalk supports the following container types for environments created with Docker containers

between April 29, 2014 and May 4, 2014:

Docker Container Types

Docker VersionAMIName

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Docker

Docker Container Types

0.9.02014.0364bit Amazon Linux 2014.03 v1.0.3 running

Docker 0.9.0

Elastic Beanstalk supports the following container types for environments created with Docker containers

prior to April 28, 2014:

Docker Container Types

Docker VersionAMIName

0.9.02014.0364bit Amazon Linux 2014.03 v1.0.2 running

Docker 0.9.0

Docker - Preconfigured

You can deploy applications to Elastic Beanstalk with Docker containers that are preconfigured to support

application88s that were developed using a specific language platform. They are included in the list of

predefined configurations (or solution stacks) as Docker - Preconfigured configurations that you can

choose when you create an environment. Elastic Beanstalk supports the following preconfigured Docker

container types:

Preconfigured Docker Container Types

Dock-

Im-

age

Name

Ap-

plic-

tion

Serv-

Proxy

Serv-

Lan-

guage

Docker VersionContainer Operating

System

AMIName

amazon/aws-

eb-

glassfish:4.1-

jdk8-

on-

build-

3.5.1

Glassfish

4.1

Nginx

1.6.2

Java

1.5.0Debian Jessie2014.0964bit Debian Jessie v1.2.1 running

Glassfish 4.1 Java 8 (Precon-

figured – Docker)

amazon/aws-

eb-

glassfish:4.0-

jdk7-

on-

build-

3.5.1

Glassfish

4.0

Nginx

1.6.2

Java

1.5.0Debian Jessie2014.0964bit Debian Jessie v1.2.1 running

Glassfish 4.0 Java 7 (Precon-

figured – Docker)

golang:1.4.1-

on-

build

Nginx

1.6.2

1.4.1

1.5.0Debian Jessie2014.0964bit Debian Jessie v1.2.1 running

Go 1.4 (Preconfigured – Docker)

golang:1.3.3-

on-

build

Nginx

1.6.2

1.3.3

1.5.0Debian Jessie2014.0964bit Debian Jessie v1.2.1 running

Go 1.3 (Preconfigured – Docker)

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Docker - Preconfigured

Preconfigured Docker Container Types

amazon/aws-

eb-

py-

thon:3.4.2-

on-

build-

3.5.1

uWSGI

2.0.8

Nginx

1.6.2

Py-

thon

3.4

1.5.0Debian Jessie2014.0964bit Debian Jessie v1.2.1 running

Python 3.4 (Preconfigured –

Docker)

Elastic Beanstalk supports the following container types for environments created with preconfigured

Docker containers between February 17, 2015 and March 23, 2015:

Preconfigured Docker Container Types

Dock-

Im-

age

Name

Ap-

plic-

tion

Serv-

Proxy

Serv-

Lan-

guage

Docker VersionContainer Operating

System

AMIName

amazon/aws-

eb-

glassfish:4.1-

jdk8-

on-

build-

3.5.1

Glassfish

4.1

Nginx

1.6.2

Java

1.3.3Debian Jessie2014.0964bit Debian Jessie v1.2.0 running

Glassfish 4.1 Java 8 (Precon-

figured – Docker)

amazon/aws-

eb-

glassfish:4.0-

jdk7-

on-

build-

3.5.1

Glassfish

4.0

Nginx

1.6.2

Java

1.3.3Debian Jessie2014.0964bit Debian Jessie v1.2.0 running

Glassfish 4.0 Java 7 (Precon-

figured – Docker)

golang:1.4.1-

on-

build

Nginx

1.6.2

1.4.1

1.3.3Debian Jessie2014.0964bit Debian Jessie v1.2.0 running

Go 1.4 (Preconfigured – Docker)

golang:1.3.3-

on-

build

Nginx

1.6.2

1.3.3

1.3.3Debian Jessie2014.0964bit Debian Jessie v1.2.0 running

Go 1.3 (Preconfigured – Docker)

amazon/aws-

eb-

py-

thon:3.4.2-

on-

build-

3.5.1

uWSGI

2.0.8

Nginx

1.6.2

Py-

thon

3.4

1.3.3Debian Jessie2014.0964bit Debian Jessie v1.2.0 running

Python 3.4 (Preconfigured –

Docker)

Elastic Beanstalk supports the following container types for environments created with preconfigured

Docker containers between February 6, 2015 and February 16, 2015:

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Docker - Preconfigured

Preconfigured Docker Container Types

Dock-

Im-

age

Name

Proxy

Serv-

Lan-

guage

Docker VersionContainer Operating

System

AMIName

golang:1.3.3-

on-

build

Nginx

1.6.2

1.3.3

1.3.3Debian Jessie2014.0964bit Debian Jessie v1.1.0 running

Go 1.3 (Preconfigured – Docker)

golang:1.4.1-

on-

build

Nginx

1.6.2

1.4.1

1.3.3Debian Jessie2014.0964bit Debian Jessie v1.1.0 running

Go 1.4 (Preconfigured – Docker)

Elastic Beanstalk supports the following container types for environments created with preconfigured

Docker containers between January 28, 2015 and February 5, 2015:

Preconfigured Docker Container Types

Dock-

Im-

age

Name

Ap-

plic-

tion

Serv-

Proxy

Serv-

Lan-

guage

Docker VersionContainer Operating

System

AMIName

amazon/aws-

eb-

glassfish:4.1-

jdk8-

on-

build-

3.5.1

Glassfish

4.1

Nginx

1.6.2

Java

1.3.3Debian Jessie2014.0964bit Debian Jessie v1.1.0

run-

ning Glassfish 4.1 Java 8 (Precon-

figured – Docker)

amazon/aws-

eb-

glassfish:4.0-

jdk7-

on-

build-

3.5.1

Glassfish

4.0

Nginx

1.6.2

Java

1.3.3Debian Jessie2014.0964bit Debian Jessie v1.1.0

run-

ning Glassfish 4.0 Java 7 (Precon-

figured – Docker)

amazon/aws-

eb-

py-

thon:3.4.2-

on-

build-

3.5.1

uWSGI

2.0.8

Nginx

1.6.2

Py-

thon

3.4

1.3.3Debian Jessie2014.0964bit Debian Jessie v1.1.0

run-

ning Python 3.4 (Preconfigured –

Docker)

Elastic Beanstalk supports the following container types for environments created with preconfigured

Docker containers between December 13, 2014 and January 27, 2015:

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Docker - Preconfigured

Preconfigured Docker Container Types

Dock-

Im-

age

Name

Ap-

plic-

tion

Serv-

Proxy

Serv-

Lan-

guage

Docker VersionContainer Operating

System

AMIName

amazon/aws-

eb-

glassfish:4.1-

jdk8-

on-

build-

3.5.1

Glassfish

4.1

Nginx

1.6.2

Java

1.3.3

Debian Jessie2014.0964bit Debian Jessie v1.0.2 running

Glassfish 4.1 Java 8 (Precon-

figured – Docker)

amazon/aws-

eb-

glassfish:4.0-

jdk7-

on-

build-

3.5.1

Glassfish

4.0

Nginx

1.6.2

Java

1.3.3

Debian Jessie2014.0964bit Debian Jessie v1.0.2 running

Glassfish 4.0 Java 7 (Precon-

figured – Docker)

amazon/aws-

eb-

py-

thon:3.4.2-

on-

build-

3.5.1

uWSGI

2.0.8

Nginx

1.6.2

Py-

thon

3.4

1.3.3

Debian Jessie2014.0964bit Debian Jessie v1.0.2 running

Python 3.4 (Preconfigured –

Docker)

Elastic Beanstalk supports the following container types for environments created with preconfigured

Docker containers between November 26, 2014 and December 12, 2014:

Preconfigured Docker Container Types

Dock-

Im-

age

Name

Ap-

plic-

tion

Serv-

Proxy

Serv-

Lan-

guage

Docker VersionContainer Operating

System

AMIName

amazon/aws-

eb-

glassfish:4.1-

jdk8-

on-

build-

3.5.1

Glassfish

4.1

Nginx

1.6.2

Java

1.3.2Debian Jessie2014.0964bit Debian Jessie v1.0.1 running

Glassfish 4.1 Java 8 (Precon-

figured – Docker)

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Docker - Preconfigured

Preconfigured Docker Container Types

amazon/aws-

eb-

glassfish:4.0-

jdk7-

on-

build-

3.5.1

Glassfish

4.0

Nginx

1.6.2

Java

1.3.2Debian Jessie2014.0964bit Debian Jessie v1.0.1 running

Glassfish 4.0 Java 7 (Precon-

figured – Docker)

amazon/aws-

eb-

py-

thon:3.4.2-

on-

build-

3.5.1

uWSGI

2.0.8

Nginx

1.6.2

Py-

thon

3.4

1.3.2Debian Jessie2014.0964bit Debian Jessie v1.0.1 running

Python 3.4 (Preconfigured –

Docker)

Elastic Beanstalk supports the following container types for environments created with preconfigured

Docker containers prior to November 25, 2014:

Preconfigured Docker Container Types

Dock-

Im-

age

Name

Ap-

plic-

tion

Serv-

Proxy

Serv-

Lan-

guage

Docker VersionContainer Operating

System

AMIName

amazon/aws-

eb-

glassfish:4.1-

jdk8-

on-

build-

3.5.1

Glassfish

4.1

Nginx

1.6.2

Java

1.2.0Debian Jessie2014.0964bit Debian Jessie v1.0.0 running

Glassfish 4.1 Java 8 (Precon-

figured – Docker)

amazon/aws-

eb-

glassfish:4.0-

jdk7-

on-

build-

3.5.1

Glassfish

4.0

Nginx

1.6.2

Java

1.2.0Debian Jessie2014.0964bit Debian Jessie v1.0.0 running

Glassfish 4.0 Java 7 (Precon-

figured – Docker)

amazon/aws-

eb-

py-

thon:3.4.2-

on-

build-

3.5.1

uWSGI

2.0.8

Nginx

1.6.2

Py-

thon

3.4

1.2.0Debian Jessie2014.0964bit Debian Jessie v1.0.0 running

Python 3.4 (Preconfigured –

Docker)

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Docker - Preconfigured

Java

You can get started with Java using the AWS Toolkit for Eclipse.The toolkit is a downloadable package

that includes the AWS libraries, project templates, code samples, and documentation.The AWS SDK for

Java supports developing applications using either Java 5 or Java 6. Elastic Beanstalk supports the

following container types:

Java Container Types

Web

Serv-

Application ServerLanguageAMIName

Apache

2.2.29

Tomcat 8Java 1.8.0_312014.0964bit Amazon Linux 2014.09

v1.1.0

running Tomcat 8 Java 8

Apache

2.2.26

Tomcat 7.0.55Java 1.7.0.512014.0964bit Amazon Linux 2014.09

v1.1.0

running Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.55Java 1.6.0_242014.0964bit Amazon Linux 2014.09

v1.1.0

running Tomcat 7 Java 6

Apache

2.2.29

Tomcat 7.0.55Java 1.7.0.712014.0332bit Amazon Linux 2014.03

v1.1.0

running Tomcat 7 Java 7

Apache

2.2.29

Tomcat 7.0.55Java 1.7.0.712014.0364bit Amazon Linux 2014.03

v1.1.0

running Tomcat 7 Java 7

Apache

2.2.29

Tomcat 7.0.55Java 1.6.0_332014.0332bit Amazon Linux 2014.03

v1.1.0

running Tomcat 7 Java 6

Apache

2.2.29

Tomcat 7.0.55Java 1.6.0_332014.0364bit Amazon Linux 2014.03

v1.1.0

running Tomcat 7 Java 6

Elastic Beanstalk supports the following container types for environments created with Java containers

between January 28, 2015 and February 16, 2015:

Java Container Types

Web

Serv-

Application ServerLanguageAMIName

Apache

2.2.29

Tomcat 8.0.15Java 1.8.0_312014.0964bit Amazon Linux 2014.09

v1.2.0 running Tomcat 8 Java 8

Apache

2.2.29

Tomcat 7.0.57Java 1.7.0.752014.0964bit Amazon Linux 2014.09

v1.2.0 running Tomcat 7 Java 7

Apache

2.2.29

Tomcat 7.0.57Java 1.6.0_332014.0964bit Amazon Linux 2014.09

v1.2.0 running Tomcat 7 Java 6

Elastic Beanstalk supports the following container types for environments created with Java containers

between November 6, 2014 and January 27, 2015:

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Java

Java Container Types

Web

Serv-

Application ServerLanguageAMIName

Apache

2.2.29

Tomcat 8Java 1.8.0_252014.0964bit Amazon Linux 2014.09

v1.0.0 running Tomcat 8 Java 8

Elastic Beanstalk supports the following container types for environments created with Java containers

between October 16, 2014 and November 5, 2014:

Java Container Types

Web

Serv-

Application ServerLanguageAMIName

Apache

2.2.26

Tomcat 7.0.55Java 1.7.0.512014.0964bit Amazon Linux 2014.09

v1.0.9

running Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.55Java 1.6.0_242014.0964bit Amazon Linux 2014.09

v1.0.9

running Tomcat 7 Java 6

Apache

2.2.26

Tomcat 7.0.55Java 1.7.0.512014.0332bit Amazon Linux 2014.03

v1.0.9

running Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.55Java 1.7.0.512014.0364bit Amazon Linux 2014.03

v1.0.9

running Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.55Java 1.6.0_242014.0332bit Amazon Linux 2014.03

v1.0.9

running Tomcat 7 Java 6

Apache

2.2.26

Tomcat 7.0.55Java 1.6.0_242014.0364bit Amazon Linux 2014.03

v1.0.9

running Tomcat 7 Java 6

Elastic Beanstalk supports the following container types for environments created with Java containers

between October 9, 2014 and October 15, 2014:

Java Container Types

Web

Serv-

Application ServerLanguageAMIName

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0.512014.0932bit Amazon Linux 2014.09

v1.0.8 running Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0.512014.0964bit Amazon Linux 2014.09

v1.0.8 running Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_242014.0932bit Amazon Linux 2014.09

v1.0.8 running Tomcat 7 Java 6

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_242014.0964bit Amazon Linux 2014.09

v1.0.8 running Tomcat 7 Java 6

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Java

Elastic Beanstalk supports the following container types for environments created with Java containers

between September 24, 2014 and October 8, 2014:

Java Container Types

Web

Serv-

Application ServerLanguageAMIName

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0.512014.0332bit Amazon Linux 2014.03

v1.0.7

running Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0.512014.0364bit Amazon Linux 2014.03

v1.0.7

running Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_242014.0332bit Amazon Linux 2014.03

v1.0.7

running Tomcat 7 Java 6

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_242014.0364bit Amazon Linux 2014.03

v1.0.7

running Tomcat 7 Java 6

Elastic Beanstalk supports the following container types for environments created with Java containers

between June 30, 2014 and September 23, 2014:

Java Container Types

Web

Serv-

Application ServerLanguageAMIName

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0.512014.0364bit Amazon Linux 2014.03

v1.0.4 running Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_242014.0364bit Amazon Linux 2014.03

v1.0.4 running Tomcat 7 Java 6

Elastic Beanstalk supports the following container types for environments created with Java containers

between June 5, 2014 and June 29, 2014:

Java Container Types

Web

Serv-

Application ServerLanguageAMIName

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0.512014.0332bit Amazon Linux 2014.03

v1.0.3

running Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0.512014.0364bit Amazon Linux 2014.03

v1.0.3

running Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_242014.0332bit Amazon Linux 2014.03

v1.0.3

running Tomcat 7 Java 6

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_242014.0364bit Amazon Linux 2014.03

v1.0.3

running Tomcat 7 Java 6

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Java

Elastic Beanstalk supports the following container types for environments created with Java containers

between May 5, 2014 and June 4, 2014:

Java Container Types

Web

Serv-

Application ServerLanguageAMIName

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0.512014.0332bit Amazon Linux 2014.03

v1.0.2 running Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0.512014.0364bit Amazon Linux 2014.03

v1.0.2 running Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_242014.0332bit Amazon Linux 2014.03

v1.0.2 running Tomcat 7 Java 6

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_242014.0364bit Amazon Linux 2014.03

v1.0.2 running Tomcat 7 Java 6

Elastic Beanstalk supports the following container types for environments created with Java containers

between April 7, 2014 and May 4, 2014:

Java Container Types

Web

Serv-

Application ServerLanguageAMIName

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0.512013.0932bit Amazon Linux 2014.02

v1.0.1

running Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0.512013.0964bit Amazon Linux 2014.02

v1.0.1

running Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_242013.0932bit Amazon Linux 2014.02

v1.0.1

running Tomcat 7 Java 6

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_242013.0964bit Amazon Linux 2014.02

v1.0.1

running Tomcat 7 Java 6

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0_252013.0932bit Amazon Linux 2013.09

v1.0.1

running Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0_252013.0964bit Amazon Linux 2013.09

v1.0.1

running Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_622013.0932bit Amazon Linux 2013.09

v1.0.1

running Tomcat 7 Java 6

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_622013.0964bit Amazon Linux 2013.09

v1.0.1

running Tomcat 7 Java 6

Apache

2.2.22

Tomcat 6.0.35Java 1.6.0_242012.0932bit Amazon Linux running

Tomcat 6

Apache

2.2.22

Tomcat 6.0.35Java 1.6.0_242012.0964bit Amazon Linux running

Tomcat 6

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Java

Elastic Beanstalk supports the following container types for environments created with Java containers

between March 18, 2014 and April 6, 2014:

Java Container Types

Web

Serv-

Application ServerLanguageAMIName

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0.512013.0932bit Amazon Linux 2014.02 run-

ning Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0.512013.0964bit Amazon Linux 2014.02 run-

ning Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_242013.0932bit Amazon Linux 2014.02 run-

ning Tomcat 7 Java 6

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_242013.0964bit Amazon Linux 2014.02 run-

ning Tomcat 7 Java 6

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0_252013.0932bit Amazon Linux 2013.09 run-

ning Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0_252013.0964bit Amazon Linux 2013.09 run-

ning Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_622013.0932bit Amazon Linux 2013.09 run-

ning Tomcat 7 Java 6

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_622013.0964bit Amazon Linux 2013.09 run-

ning Tomcat 7 Java 6

Apache

2.2.22

Tomcat 6.0.35Java 1.6.0_242012.0932bit Amazon Linux running

Tomcat 6

Apache

2.2.22

Tomcat 6.0.35Java 1.6.0_242012.0964bit Amazon Linux running

Tomcat 6

Elastic Beanstalk supports the following container types for environments created with Java containers

between November 7, 2013 and March 17, 2014:

Java Container Types

Web

Serv-

Application ServerLanguageAMIName

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0_252013.0932bit Amazon Linux 2013.09 run-

ning Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.7.0_252013.0964bit Amazon Linux 2013.09 run-

ning Tomcat 7 Java 7

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_622013.0932bit Amazon Linux 2013.09 run-

ning Tomcat 7 Java 6

Apache

2.2.26

Tomcat 7.0.47Java 1.6.0_622013.0964bit Amazon Linux 2013.09 run-

ning Tomcat 7 Java 6

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Java

Java Container Types

Apache

2.2.22

Tomcat 6.0.35Java 1.6.0_242012.0932bit Amazon Linux running

Tomcat 6

Apache

2.2.22

Tomcat 6.0.35Java 1.6.0_242012.0964bit Amazon Linux running

Tomcat 6

Elastic Beanstalk supports the following container types for environments created with Java containers

prior to November 6, 2013:

Java Container Types

Web

Serv-

Application ServerLanguageAMIName

Apache

2.2.22

Tomcat 7.0.27Java 1.6.0_242012.0932bit Amazon Linux running

Tomcat 7

Apache

2.2.22

Tomcat 7.0.27Java 1.6.0_242012.0964bit Amazon Linux running

Tomcat 7

Windows and .NET

You can get started in minutes using the AWS Toolkit for Visual Studio.The toolkit includes the AWS

libraries, project templates, code samples, and documentation.The AWS SDK for .NET supports the

development of applications using .NET Framework 2.0 or later. To learn how to get started deploying a

.NET application using the AWS Toolkit for Visual Studio, see Creating and Deploying Elastic Beanstalk

Applications in .NET Using AWS Toolkit for Visual Studio (p.125). Elastic Beanstalk supports the following

container types:

.NET Container Types

Web ServerLanguageAMIName

IIS 8.5v1.0

v1.1

v2.0

v3.0

v3.5

v4.0/v4.5

Custom64bit Windows Server 2012 R2

running IIS 8.5

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Windows and .NET

.NET Container Types

IIS 8.5v1.0

v1.1

v2.0

v3.0

v3.5

v4.0/v4.5

Custom64bit Windows Server Core

2012 R2

running IIS 8.5

Elastic Beanstalk supports the following container types for environments created with .NET containers

prior to August 6, 2014:

.NET Container Types

Web ServerLanguageAMIName

IIS 8v1.0

v1.1

v2.0

v3.0

v3.5

v4.0/v4.5

Custom64bit Windows Server 2012

running IIS 8

IIS 7.5v1.0

v1.1

v2.0

v3.0

v3.5

v4.0/v4.5

Custom64bit Windows Server 2008 R2

running IIS 7.5

Node.js

You can get started in minutes using the AWS Management Console or the eb command line interface.

You can deploy applications by simply zipping them up and uploading them through the console.To learn

how to upload an application using the AWS Management Console, see Creating New Applications (p.279).

To learn how to get started deploying a Node.js application to Elastic Beanstalk using eb and Git, see

Deploying Elastic Beanstalk Applications in Node.js Using EB CLI and Git (p. 174). Elastic Beanstalk

supports the following container types:

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Node.js

Node.js Container Types

Web

Serv-

Node.js VersionLanguageAMIName

Nginx

1.6.2

Apache

2.4.10

0.8.26

0.8.28

0.10.21

0.10.26

0.10.31

0.12.0

JavaScript2014.0964bit Amazon Linux 2014.09

v1.2.1 running Node.js

Elastic Beanstalk supports the following container types for environments created with Node.js containers

between February 17, 2015 and March 23, 2015:

Node.js Container Types

Web

Serv-

Node.js VersionLanguageAMIName

Nginx

1.6.2

Apache

2.4.10

0.8.26

0.8.28

0.10.21

0.10.26

0.10.31

JavaScript2014.0964bit Amazon Linux 2014.09

v1.2.0 running Node.js

Elastic Beanstalk supports the following container types for environments created with Node.js containers

between January 28, 2015 and February 16, 2015:

Node.js Container Types

Web

Serv-

Node.js VersionLanguageAMIName

Nginx

1.6.2

Apache

2.4.6

0.8.26

0.8.28

0.10.21

0.10.26

0.10.31

JavaScript2014.0964bit Amazon Linux 2014.09

v1.1.0

running Node.js

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Node.js

Node.js Container Types

Nginx

1.4.7

Apache

2.4.10

0.8.26

0.8.28

0.10.21

0.10.26

0.10.31

JavaScript2014.0332bit Amazon Linux 2014.03

v1.1.0

running Node.js

Nginx

1.4.7

Apache

2.4.10

0.8.26

0.8.28

0.10.21

0.10.26

0.10.31

JavaScript2014.0364bit Amazon Linux 2014.03

v1.1.0

running Node.js

Elastic Beanstalk supports the following container types for environments created with Node.js containers

between October 16, 2014 and January 27, 2015:

Node.js Container Types

Web

Serv-

Node.js VersionLanguageAMIName

Nginx

1.6.2

Apache

2.4.6

0.8.26

0.8.28

0.10.21

0.10.26

0.10.31

JavaScript2014.0964bit Amazon Linux 2014.09

v1.0.9

running Node.js

Nginx

1.6.2

Apache

2.4.6

0.8.26

0.8.28

0.10.21

0.10.26

0.10.31

JavaScript2014.0332bit Amazon Linux 2014.03

v1.0.9

running Node.js

Nginx

1.6.2

Apache

2.4.6

0.8.26

0.8.28

0.10.21

0.10.26

0.10.31

JavaScript2014.0364bit Amazon Linux 2014.03

v1.0.9

running Node.js

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Node.js

Elastic Beanstalk supports the following container types for environments created with Node.js containers

between October 9, 2014 and October 15, 2014:

Node.js Container Types

Web

Serv-

Node.js VersionLanguageAMIName

Nginx

1.4.7

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.8.26

0.10.10

0.10.21

0.10.26

JavaScript2014.0964bit Amazon Linux 2014.09

v1.0.8 running Node.js

Elastic Beanstalk supports the following container types for environments created with Node.js containers

between September 24, 2014 and October 8, 2014:

Node.js Container Types

Web

Serv-

Node.js VersionLanguageAMIName

Nginx

1.4.7

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.8.26

0.10.10

0.10.21

0.10.26

JavaScript2014.0332bit Amazon Linux 2014.03

v1.0.7

running Node.js

Nginx

1.4.7

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.8.26

0.10.10

0.10.21

0.10.26

JavaScript2014.0364bit Amazon Linux 2014.03

v1.0.7

running Node.js

Elastic Beanstalk supports the following container types for environments created with Node.js containers

between June 30, 2014 and September 23, 2014:

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Node.js

Node.js Container Types

Web

Serv-

Node.js VersionLanguageAMIName

Nginx

1.4.7

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.8.26

0.10.10

0.10.21

0.10.26

JavaScript2014.0364bit Amazon Linux 2014.03

v1.0.4 running Node.js

Elastic Beanstalk supports the following container types for environments created with Node.js containers

between June 5, 2014 and June 29, 2014:

Node.js Container Types

Web

Serv-

Node.js VersionLanguageAMIName

Nginx

1.4.7

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.8.26

0.10.10

0.10.21

0.10.26

JavaScript2014.0332bit Amazon Linux 2014.03

v1.0.3

running Node.js

Nginx

1.4.7

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.8.26

0.10.10

0.10.21

0.10.26

JavaScript2014.0364bit Amazon Linux 2014.03

v1.0.3

running Node.js

Elastic Beanstalk supports the following container types for environments created with Node.js containers

between May 5, 2014 and June 4, 2014:

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Node.js

Node.js Container Types

Web

Serv-

Node.js VersionLanguageAMIName

Nginx

1.4.7

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.8.26

0.10.10

0.10.21

0.10.26

JavaScript2014.0332bit Amazon Linux 2014.03

v1.0.2 running Node.js

Nginx

1.4.7

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.8.26

0.10.10

0.10.21

0.10.26

JavaScript2014.0364bit Amazon Linux 2014.03

v1.0.2 running Node.js

Elastic Beanstalk supports the following container types for environments created with Node.js containers

between April 7, 2014 and May 4, 2014:

Node.js Container Types

Web

Serv-

Node.js VersionLanguageAMIName

Nginx

1.4.3

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.8.26

0.10.10

0.10.21

0.10.26

JavaScript2013.0932bit Amazon Linux 2014.02

v1.0.1

running Node.js

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Node.js

Node.js Container Types

Nginx

1.4.3

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.8.26

0.10.10

0.10.21

0.10.26

JavaScript2013.0964bit Amazon Linux 2014.02

v1.0.1

running Node.js

Nginx

1.4.3

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.10.10

0.10.21

JavaScript2013.0932bit Amazon Linux 2013.09

v1.0.1

running Node.js

Nginx

1.4.3

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.10.10

0.10.21

JavaScript2013.0964bit Amazon Linux 2013.09

v1.0.1

running Node.js

Elastic Beanstalk supports the following container types for environments created with Node.js containers

between March 18, 2014 and April 6, 2014:

Node.js Container Types

Web

Serv-

Node.js VersionLanguageAMIName

Nginx

1.4.3

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.8.26

0.10.10

0.10.21

0.10.26

JavaScript2013.0932bit Amazon Linux 2014.02

running Node.js

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Node.js

Node.js Container Types

Nginx

1.4.3

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.8.26

0.10.10

0.10.21

0.10.26

JavaScript2013.0964bit Amazon Linux 2014.02

running Node.js

Nginx

1.4.3

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.10.10

0.10.21

JavaScript2013.0932bit Amazon Linux 2013.09

running Node.js

Nginx

1.4.3

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.10.10

0.10.21

JavaScript2013.0964bit Amazon Linux 2013.09

running Node.js

Elastic Beanstalk supports the following container types for environments created with Node.js containers

between October 29, 2013 and March 17, 2014:

Node.js Container Types

Web

Serv-

Node.js VersionLanguageAMIName

Nginx

1.4.3

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.10.10

0.10.21

JavaScript2013.0932bit Amazon Linux 2013.09

running Node.js

Nginx

1.4.3

Apache

2.4.6

0.8.6 through 0.8.21

0.8.24

0.10.10

0.10.21

JavaScript2013.0964bit Amazon Linux 2013.09

running Node.js

Elastic Beanstalk supports the following container types for environments created with Node.js containers

between August 15, 2013 and October 28, 2013:

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Node.js

Node.js Container Types

Web

Serv-

Node.js VersionLanguageAMIName

Nginx

1.2.9

Apache

2.4.4

0.8.6 through 0.8.21

0.8.24

0.10.10

JavaScript2013.0332bit Amazon Linux running

Node.js

Nginx

1.2.9

Apache

2.4.4

0.8.6 through 0.8.21

0.8.24

0.10.10

JavaScript2013.0364bit Amazon Linux running

Node.js

Elastic Beanstalk supports the following container types for environments created with Node.js containers

prior to August 15, 2013:

Node.js Container Types

Web

Serv-

Node.js VersionLanguageAMIName

Nginx

1.2.6

Apache

2.4.3

0.8.6 through 0.8.21

0.8.24

JavaScript2012.0932bit Amazon Linux 2012.09

running Node.js

Nginx

1.2.6

Apache

2.4.3

0.8.6 through 0.8.21

0.8.24

JavaScript2012.0964bit Amazon Linux 2012.09

running Node.js

PHP

You can get started in minutes using the AWS Management Console or the eb command line interface.

You can deploy applications by simply zipping them up and uploading them through the console.To learn

how to upload an application using the AWS Management Console, see Creating New Applications (p.279).

To learn how to get started deploying a PHP application to Elastic Beanstalk using eb and Git, see

Deploying Elastic Beanstalk Applications in PHP (p.220). Elastic Beanstalk supports the following container

types:

PHP Container Types

Web ServerLanguageAMIName

Apache 2.4.10PHP 5.5.202014.0964bit Amazon Linux 2014.09

v1.2.0 running PHP 5.5

API Version 2010-12-01

Elastic Beanstalk Developer Guide

PHP

PHP Container Types

Apache 2.4.10PHP 5.4.362014.0964bit Amazon Linux 2014.09

v1.2.0 running PHP 5.4

Elastic Beanstalk supports the following container types for environments created with PHP containers

between January 28, 2015 and February 16, 2015:

PHP Container Types

Web ServerLanguageAMIName

Apache 2.4.6PHP 5.5.72014.0964bit Amazon Linux 2014.09

v1.1.0

running PHP 5.5

Apache 2.4.6PHP 5.4.202014.0964bit Amazon Linux 2014.09

v1.1.0

running PHP 5.4

Apache 2.4.10PHP 5.5.142014.0332bit Amazon Linux 2014.03

v1.1.0

running PHP 5.5

Apache 2.4.10PHP 5.5.142014.0364bit Amazon Linux 2014.03

v1.1.0

running PHP 5.5

Apache 2.4.10PHP 5.4.302014.0332bit Amazon Linux 2014.03

v1.1.0

running PHP 5.4

Apache 2.4.10PHP 5.4.302014.0364bit Amazon Linux 2014.03

v1.1.0

running PHP 5.4

Elastic Beanstalk supports the following container types for environments created with PHP containers

between October 16, 2014 and January 27, 2015:

PHP Container Types

Web ServerLanguageAMIName

Apache 2.4.6PHP 5.5.72014.0964bit Amazon Linux 2014.09

v1.0.9

running PHP 5.5

Apache 2.4.6PHP 5.4.202014.0964bit Amazon Linux 2014.09

v1.0.9

running PHP 5.4

Apache 2.4.6PHP 5.5.72014.0332bit Amazon Linux 2014.03

v1.0.9

running PHP 5.5

Apache 2.4.6PHP 5.5.72014.0364bit Amazon Linux 2014.03

v1.0.9

running PHP 5.5

Apache 2.4.6PHP 5.4.202014.0332bit Amazon Linux 2014.03

v1.0.9

running PHP 5.4

Apache 2.4.6PHP 5.4.202014.0364bit Amazon Linux 2014.03

v1.0.9

running PHP 5.4

Elastic Beanstalk supports the following container types for environments created with PHP containers

between October 9, 2014 and October 15, 2014:

API Version 2010-12-01

Elastic Beanstalk Developer Guide

PHP

PHP Container Types

Web ServerLanguageAMIName

Apache 2.4.6PHP 5.5.72014.0932bit Amazon Linux 2014.09

v1.0.8 running PHP 5.5

Apache 2.4.6PHP 5.5.72014.0964bit Amazon Linux 2014.09

v1.0.8 running PHP 5.5

Apache 2.4.6PHP 5.4.202014.0932bit Amazon Linux 2014.09

v1.0.8 running PHP 5.4

Apache 2.4.6PHP 5.4.202014.0964bit Amazon Linux 2014.09

v1.0.8 running PHP 5.4

Elastic Beanstalk supports the following container types for environments created with PHP containers

between September 24, 2014 and October 8, 2014:

PHP Container Types

Web ServerLanguageAMIName

Apache 2.4.6PHP 5.5.72014.0332bit Amazon Linux 2014.03

v1.0.7

running PHP 5.5

Apache 2.4.6PHP 5.5.72014.0364bit Amazon Linux 2014.03

v1.0.7

running PHP 5.5

Apache 2.4.6PHP 5.4.202014.0332bit Amazon Linux 2014.03

v1.0.7

running PHP 5.4

Apache 2.4.6PHP 5.4.202014.0364bit Amazon Linux 2014.03

v1.0.7

running PHP 5.4

Elastic Beanstalk supports the following container types for environments created with PHP containers

between June 30, 2014 and September 23, 2014:

PHP Container Types

Web ServerLanguageAMIName

Apache 2.4.6PHP 5.5.72014.0364bit Amazon Linux 2014.03

v1.0.4 running PHP 5.5

Apache 2.4.6PHP 5.4.202014.0364bit Amazon Linux 2014.03

v1.0.4 running PHP 5.4

Elastic Beanstalk supports the following container types for environments created with PHP containers

between June 5, 2014 and June 29, 2014:

PHP Container Types

Web ServerLanguageAMIName

Apache 2.4.6PHP 5.5.72014.0332bit Amazon Linux 2014.03

v1.0.3

running PHP 5.5

API Version 2010-12-01

Elastic Beanstalk Developer Guide

PHP

PHP Container Types

Apache 2.4.6PHP 5.5.72014.0364bit Amazon Linux 2014.03

v1.0.3

running PHP 5.5

Apache 2.4.6PHP 5.4.202014.0332bit Amazon Linux 2014.03

v1.0.3

running PHP 5.4

Apache 2.4.6PHP 5.4.202014.0364bit Amazon Linux 2014.03

v1.0.3

running PHP 5.4

Elastic Beanstalk supports the following container types for environments created with PHP containers

between May 5, 2014 and June 4, 2014:

PHP Container Types

Web ServerLanguageAMIName

Apache 2.4.6PHP 5.5.72014.0332bit Amazon Linux 2014.03

v1.0.2 running PHP 5.5

Apache 2.4.6PHP 5.5.72014.0364bit Amazon Linux 2014.03

v1.0.2 running PHP 5.5

Apache 2.4.6PHP 5.4.202014.0332bit Amazon Linux 2014.03

v1.0.2 running PHP 5.4

Apache 2.4.6PHP 5.4.202014.0364bit Amazon Linux 2014.03

v1.0.2 running PHP 5.4

Elastic Beanstalk supports the following container types for environments created with PHP containers

between April 7, 2014 and May 4, 2014:

PHP Container Types

Web ServerLanguageAMIName

Apache 2.4.6PHP 5.5.72013.0932bit Amazon Linux 2014.02

v1.0.1

running PHP 5.5

Apache 2.4.6PHP 5.5.72013.0964bit Amazon Linux 2014.02

v1.0.1

running PHP 5.5

Apache 2.4.6PHP 5.4.202013.0932bit Amazon Linux 2014.02

v1.0.1

running PHP 5.4

Apache 2.4.6PHP 5.4.202013.0964bit Amazon Linux 2014.02

v1.0.1

running PHP 5.4

Apache 2.4.6PHP 5.52013.0932bit Amazon Linux 2013.09

v1.0.1

running PHP 5.5

Apache 2.4.6PHP 5.52013.0964bit Amazon Linux 2013.09

v1.0.1

running PHP 5.5

Apache 2.4.6PHP 5.42013.0932bit Amazon Linux 2013.09

v1.0.1

running PHP 5.4

API Version 2010-12-01

Elastic Beanstalk Developer Guide

PHP

PHP Container Types

Apache 2.4.6PHP 5.42013.0964bit Amazon Linux 2013.09

v1.0.1

running PHP 5.4

Apache 2.4.6PHP 5.32013.0332bit Amazon Linux running

PHP 5.3

Apache 2.4.6PHP 5.32013.0364bit Amazon Linux running

PHP 5.3

Elastic Beanstalk supports the following container types for environments created with PHP containers

between March 18, 2014 and April 6, 2014:

PHP Container Types

Web ServerLanguageAMIName

Apache 2.2.26PHP 5.5.72013.0932bit Amazon Linux 2014.02

running PHP 5.5

Apache 2.2.26PHP 5.5.72013.0964bit Amazon Linux 2014.02

running PHP 5.5

Apache 2.2.26PHP 5.4.202013.0932bit Amazon Linux 2014.02

running PHP 5.4

Apache 2.2.26PHP 5.4.202013.0964bit Amazon Linux 2014.02

running PHP 5.4

Apache 2.4.6PHP 5.52013.0932bit Amazon Linux 2013.09

running PHP 5.5

Apache 2.4.6PHP 5.52013.0964bit Amazon Linux 2013.09

running PHP 5.5

Apache 2.4.6PHP 5.42013.0932bit Amazon Linux 2013.09

running PHP 5.4

Apache 2.4.6PHP 5.42013.0964bit Amazon Linux 2013.09

running PHP 5.4

Apache 2.4.6PHP 5.32013.0332bit Amazon Linux running

PHP 5.3

Apache 2.4.6PHP 5.32013.0364bit Amazon Linux running

PHP 5.3

Elastic Beanstalk supports the following container types for environments created with PHP containers

between October 30, 2013 and March 17, 2014:

PHP Container Types

Web ServerLanguageAMIName

Apache 2.4.6PHP 5.52013.0932bit Amazon Linux 2013.09

running PHP 5.5

API Version 2010-12-01

Elastic Beanstalk Developer Guide

PHP

PHP Container Types

Apache 2.4.6PHP 5.52013.0964bit Amazon Linux 2013.09

running PHP 5.5

Apache 2.4.6PHP 5.42013.0932bit Amazon Linux 2013.09

running PHP 5.4

Apache 2.4.6PHP 5.42013.0964bit Amazon Linux 2013.09

running PHP 5.4

Apache 2.4.6PHP 5.32013.0332bit Amazon Linux running

PHP 5.3

Apache 2.4.6PHP 5.32013.0364bit Amazon Linux running

PHP 5.3

Elastic Beanstalk supports the following container types for environments created with PHP containers

between August 29, 2013 and October 29, 2013:

PHP Container Types

Web ServerLanguageAMIName

Apache 2.4.6PHP 5.42013.0332bit Amazon Linux running

PHP 5.4

Apache 2.4.6PHP 5.42013.0364bit Amazon Linux running

PHP 5.4

Elastic Beanstalk supports the following container types for environments created with PHP containers

prior to August 29, 2013:

PHP Container Types

Web ServerLanguageAMIName

Apache 2.4.3PHP 5.42012.0932bit Amazon Linux 2012.09

running PHP 5.4

Apache 2.4.3PHP 5.42012.0964bit Amazon Linux 2012.09

running PHP 5.4

Apache 2.4.3PHP 5.32012.0932bit Amazon Linux 2012.09

running PHP 5.3

Apache 2.4.3PHP 5.32012.0964bit Amazon Linux 2012.09

running PHP 5.3

Python

Elastic Beanstalk supports Python applications running on Apache and WSGI.This includes support for

many popular frameworks such as Django and Flask.You can get started in minutes using the AWS

Management Console or the eb command line interface.You can deploy applications by simply zipping

them up and uploading them through the console.To learn how to upload an application using the AWS

Management Console, see Creating New Applications (p. 279). To learn how to get started deploying a

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Python

Python application to Elastic Beanstalk using eb and Git, see Deploying Elastic Beanstalk Applications

in Python Using EB CLI and Git (p. 242). Elastic Beanstalk supports the following container types:

Python Container Types

Web ServerLanguageAMIName

Apache 2.4.10 with

mod_wsgi 3.5

Python 2.7.82014.0964bit Amazon Linux 2014.09

v1.2.0 running Python 2.7

Apache 2.4.10 with

mod_wsgi 3.5

Python 2.6.92014.0964bit Amazon Linux 2014.09

v1.2.0 running Python 2.6

Elastic Beanstalk supports the following container types for environments created with Python containers

between January 28, 2015 and February 16, 2015:

Python Container Types

Web ServerLanguageAMIName

Apache 2.4.10 with

mod_wsgi 3.5

Python 2.7.52014.0964bit Amazon Linux 2014.09

v1.1.0

running Python 2.7

Apache 2.4.10 with

mod_wsgi 3.5

Python 2.6.92014.0964bit Amazon Linux 2014.09

v1.1.0

running Python

Apache 2.4.10 with

mod_wsgi 3.2

Python 2.7.52014.0332bit Amazon Linux 2014.03

v1.1.0

running Python 2.7

Apache 2.4.10 with

mod_wsgi 3.2

Python 2.7.52014.0364bit Amazon Linux 2014.03

v1.1.0

running Python 2.7

Apache 2.4.10 with

mod_wsgi 3.2

Python 2.6.92014.0332bit Amazon Linux 2014.03

v1.1.0

running Python

Apache 2.4.10 with

mod_wsgi 3.2

Python 2.6.92014.0364bit Amazon Linux 2014.03

v1.1.0

running Python

Elastic Beanstalk supports the following container types for environments created with Python containers

between October 31, 2014 and January 27, 2015:

Python Container Types

Web ServerLanguageAMIName

Apache 2.4.10 with

mod_wsgi 3.5

Python 2.7.52014.0964bit Amazon Linux 2014.09

v1.0.9 running Python 2.7

Apache 2.4.10 with

mod_wsgi 3.5

Python 2.6.92014.0964bit Amazon Linux 2014.09

v1.0.9 running Python

Elastic Beanstalk supports the following container types for environments created with Python containers

between October 16, 2014 and October 30, 2014:

Python Container Types

Web ServerLanguageAMIName

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Python

Python Container Types

Apache with mod_wsgi 3.2Python 2.72014.0332bit Amazon Linux 2014.03

v1.0.9

running Python 2.7

Apache with mod_wsgi 3.2Python 2.72014.0364bit Amazon Linux 2014.03

v1.0.9

running Python 2.7

Apache with mod_wsgi 3.2Python 2.62014.0332bit Amazon Linux 2014.03

v1.0.9

running Python

Apache with mod_wsgi 3.2Python 2.62014.0364bit Amazon Linux 2014.03

v1.0.9

running Python

Elastic Beanstalk supports the following container types for environments created with Python containers

between September 24, 2014 and October 15, 2014:

Python Container Types

Web ServerLanguageAMIName

Apache with mod_wsgi 3.2Python 2.72014.0332bit Amazon Linux 2014.03

v1.0.7

running Python 2.7

Apache with mod_wsgi 3.2Python 2.72014.0364bit Amazon Linux 2014.03

v1.0.7

running Python 2.7

Apache with mod_wsgi 3.2Python 2.62014.0332bit Amazon Linux 2014.03

v1.0.7

running Python

Apache with mod_wsgi 3.2Python 2.62014.0364bit Amazon Linux 2014.03

v1.0.7

running Python

Elastic Beanstalk supports the following container types for environments created with Python containers

between June 30, 2014 and September 23, 2014:

Python Container Types

Web ServerLanguageAMIName

Apache with mod_wsgi 3.2Python 2.72014.0364bit Amazon Linux 2014.03

v1.0.4 running Python 2.7

Apache with mod_wsgi 3.2Python 2.62014.0364bit Amazon Linux 2014.03

v1.0.4 running Python

Elastic Beanstalk supports the following container types for environments created with Python containers

between June 5, 2014 and June 29, 2014:

Python Container Types

Web ServerLanguageAMIName

Apache with mod_wsgi 3.2Python 2.72014.0332bit Amazon Linux 2014.03

v1.0.3

running Python 2.7

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Python

Python Container Types

Apache with mod_wsgi 3.2Python 2.72014.0364bit Amazon Linux 2014.03

v1.0.3

running Python 2.7

Apache with mod_wsgi 3.2Python 2.62014.0332bit Amazon Linux 2014.03

v1.0.3

running Python

Apache with mod_wsgi 3.2Python 2.62014.0364bit Amazon Linux 2014.03

v1.0.3

running Python

Elastic Beanstalk supports the following container types for environments created with Python containers

between May 5, 2014 and June 4, 2014:

Python Container Types

Web ServerLanguageAMIName

Apache with mod_wsgi 3.2Python 2.72014.0332bit Amazon Linux 2014.03

v1.0.2 running Python 2.7

Apache with mod_wsgi 3.2Python 2.72014.0364bit Amazon Linux 2014.03

v1.0.2 running Python 2.7

Apache with mod_wsgi 3.2Python 2.62014.0332bit Amazon Linux 2014.03

v1.0.2 running Python

Apache with mod_wsgi 3.2Python 2.62014.0364bit Amazon Linux 2014.03

v1.0.2 running Python

Elastic Beanstalk supports the following container types for environments created with Python containers

between April 7, 2014 and May 4, 2014:

Python Container Types

Web ServerLanguageAMIName

Apache with mod_wsgi 3.2Python 2.72013.0932bit Amazon Linux 2013.09

v1.0.1

running Python 2.7

Apache with mod_wsgi 3.2Python 2.72013.0964bit Amazon Linux 2013.09

v1.0.1

running Python 2.7

Apache with mod_wsgi 3.2Python 2.62013.0932bit Amazon Linux 2013.09

v1.0.1

running Python

Apache with mod_wsgi 3.2Python 2.62013.0964bit Amazon Linux 2013.09

v1.0.1

running Python

Elastic Beanstalk supports the following container types for environments created with Python containers

between November 7, 2013 and April 6, 2014:

Python Container Types

Web ServerLanguageAMIName

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Python

Python Container Types

Apache with mod_wsgi 3.2Python 2.72013.0932bit Amazon Linux 2013.09

running Python 2.7

Apache with mod_wsgi 3.2Python 2.72013.0964bit Amazon Linux 2013.09

running Python 2.7

Apache with mod_wsgi 3.2Python 2.62013.0932bit Amazon Linux 2013.09

running Python

Apache with mod_wsgi 3.2Python 2.62013.0964bit Amazon Linux 2013.09

running Python

Elastic Beanstalk supports the following container types for environments created with Python containers

prior to November 7, 2013:

Python Container Types

Web ServerLanguageAMIName

Apache with mod_wsgi 3.2Python 2.62012.0932bit Amazon Linux running

Python

Apache with mod_wsgi 3.2Python 2.62012.0964bit Amazon Linux running

Python

Ruby

Elastic Beanstalk runs Ruby applications including support for many popular frameworks such as Rails

and Sinatra.You can deploy applications in minutes using the eb command line interface and Git or the

AWS Management Console.To learn how to get started deploying a Ruby application to Elastic Beanstalk

using eb and Git, see Deploying Elastic Beanstalk Applications in Ruby Using EB CLI and Git (p. 262).To

learn how to upload an application using the AWS Management Console, see Creating New

Applications (p. 279). Elastic Beanstalk supports the following container types:

Ruby Container Types

Application/Web ServerLanguageAMIName

Puma 2.9.1 and Nginx

1.6.2

Ruby 2.2.12014.0964bit Amazon Linux 2014.09

v1.2.1 running Ruby 2.2

(Puma)

Passenger 4.0.59 and

Nginx 1.6.2

Ruby 2.2.12014.0964bit Amazon Linux 2014.09

v1.2.1 running Ruby 2.2 (Pas-

senger Standalone)

Puma 2.9.1 and Nginx

1.6.2

Ruby 2.1.5-p2732014.0964bit Amazon Linux 2014.09

v1.2.0 running Ruby 2.1

(Puma)

Passenger 4.0.53 and

Nginx 1.6.2

Ruby 2.1.5-p2732014.0964bit Amazon Linux 2014.09

v1.2.0 running Ruby 2.1 (Pas-

senger Standalone)

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Ruby

Ruby Container Types

Puma 2.9.1 and Nginx

1.6.2

Ruby 2.0.0-p5982014.0964bit Amazon Linux 2014.09

v1.2.0 running Ruby 2.0

(Puma)

Passenger 4.0.53 and

Nginx 1.6.2

Ruby 2.0.0-p5982014.0964bit Amazon Linux 2014.09

v1.2.0 running Ruby 2.0 (Pas-

senger Standalone)

Passenger 4.0.53 and

Nginx 1.6.2

Ruby 1.9.3-p5512014.0964bit Amazon Linux 2014.09

v1.2.0 running Ruby 1.9.3

Elastic Beanstalk supports the following container types for environments created with Ruby containers

between February 17, 2015 and March 23, 2015:

Ruby Container Types

Application/Web ServerLanguageAMIName

Puma 2.9.1 and Nginx

1.6.2

Ruby 2.1.5-p2732014.0964bit Amazon Linux 2014.09

v1.2.0 running Ruby 2.1

(Puma)

Passenger 4.0.53 and

Nginx 1.6.2

Ruby 2.1.5-p2732014.0964bit Amazon Linux 2014.09

v1.2.0 running Ruby 2.1 (Pas-

senger Standalone)

Puma 2.9.1 and Nginx

1.6.2

Ruby 2.0.0-p5982014.0964bit Amazon Linux 2014.09

v1.2.0 running Ruby 2.0

(Puma)

Passenger 4.0.53 and

Nginx 1.6.2

Ruby 2.0.0-p5982014.0964bit Amazon Linux 2014.09

v1.2.0 running Ruby 2.0 (Pas-

senger Standalone)

Passenger 4.0.53 and

Nginx 1.6.2

Ruby 1.9.3-p5512014.0964bit Amazon Linux 2014.09

v1.2.0 running Ruby 1.9.3

Elastic Beanstalk supports the following container types for environments created with Ruby containers

between January 28, 2015 and February 16, 2015:

Ruby Container Types

Application/Web ServerLanguageAMIName

Puma 2.9.1 and Nginx

1.6.2

Ruby 2.1.42014.0964bit Amazon Linux 2014.09

v1.1.0

running Ruby 2.1

(Puma)

Passenger 4.0.53Ruby 2.1.42014.0964bit Amazon Linux 2014.09

v1.1.0

running Ruby 2.1

(Passenger Standalone)

Puma 2.9.1 and Nginx

1.6.2

Ruby 2.0.0-p5942014.0964bit Amazon Linux 2014.09

v1.1.0

running Ruby 2.0

(Puma)

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Ruby

Ruby Container Types

Passenger 4.0.53Ruby 2.0.0-p5942014.0964bit Amazon Linux 2014.09

v1.1.0

running Ruby 2.0

(Passenger Standalone)

Passenger 4.0.53Ruby 1.9.3-p5502014.0964bit Amazon Linux 2014.09

v1.1.0

running Ruby 1.9.3

Puma 2.8.1 and Nginx

1.4.7

Ruby 2.1.2-p952014.0364bit Amazon Linux 2014.03

v1.1.0

running Ruby 2.1

(Puma)

Passenger 4.0.37Ruby 2.1.22014.0364bit Amazon Linux 2014.03

v1.1.0

running Ruby 2.1

(Passenger Standalone)

Puma 2.8.1 and Nginx

1.4.7

Ruby 2.0.0-p4812014.0364bit Amazon Linux 2014.03

v1.1.0

running Ruby 2.0

(Puma)

Passenger 4.0.37Ruby 2.0.02014.0364bit Amazon Linux 2014.03

v1.1.0

running Ruby 2.0

(Passenger Standalone)

Passenger 4.0.37Ruby 1.9.32014.0332bit Amazon Linux 2014.03

v1.1.0

running Ruby 1.9.3

Passenger 4.0.37Ruby 1.9.32014.0364bit Amazon Linux 2014.03

v1.1.0

running Ruby 1.9.3

Elastic Beanstalk supports the following container types for environments created with Ruby containers

between October 31, 2014 and January 27, 2015:

Ruby Container Types

Application/Web ServerLanguageAMIName

Puma 2.9.1 and Nginx

1.6.2

Ruby 2.1.42014.0964bit Amazon Linux 2014.09

v1.0.9 running Ruby 2.1

(Puma)

Passenger 4.0.53Ruby 2.1.42014.0964bit Amazon Linux 2014.09

v1.0.9 running Ruby 2.1 (Pas-

senger Standalone)

Puma 2.9.1 and Nginx

1.6.2

Ruby 2.0.0-p5942014.0964bit Amazon Linux 2014.09

v1.0.9 running Ruby 2.0

(Puma)

Passenger 4.0.53Ruby 2.0.0-p5942014.0964bit Amazon Linux 2014.09

v1.0.9 running Ruby 2.0 (Pas-

senger Standalone)

Passenger 4.0.53Ruby 1.9.3-p5502014.0964bit Amazon Linux 2014.09

v1.0.9 running Ruby 1.9.3

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Ruby

Elastic Beanstalk supports the following container types for environments created with Ruby containers

between October 16, 2014 and October 30, 2014:

Ruby Container Types

Application/Web ServerLanguageAMIName

Puma 2.8.1 and Nginx

1.4.7

Ruby 2.1.22014.0364bit Amazon Linux 2014.03

v1.0.9

running Ruby 2.1

(Puma)

Passenger 4.0.37Ruby 2.1.22014.0364bit Amazon Linux 2014.03

v1.0.9

running Ruby 2.1

(Passenger Standalone)

Puma 2.8.1 and Nginx

1.4.7

Ruby 2.0.02014.0364bit Amazon Linux 2014.03

v1.0.9

running Ruby 2.0

(Puma)

Passenger 4.0.37Ruby 2.0.02014.0364bit Amazon Linux 2014.03

v1.0.9

running Ruby 2.0

(Passenger Standalone)

Passenger 4.0.37Ruby 1.9.32014.0332bit Amazon Linux 2014.03

v1.0.9

running Ruby 1.9.3

Passenger 4.0.37Ruby 1.9.32014.0364bit Amazon Linux 2014.03

v1.0.9

running Ruby 1.9.3

Elastic Beanstalk supports the following container types for environments created with Ruby containers

between September 24, 2014 and October 15, 2014:

Ruby Container Types

Application/Web ServerLanguageAMIName

Puma 2.8.1 and Nginx

1.4.7

Ruby 2.1.22014.0364bit Amazon Linux 2014.03

v1.0.7

running Ruby 2.1

(Puma)

Passenger 4.0.37Ruby 2.1.22014.0364bit Amazon Linux 2014.03

v1.0.7

running Ruby 2.1

(Passenger Standalone)

Puma 2.8.1 and Nginx

1.4.7

Ruby 2.0.02014.0364bit Amazon Linux 2014.03

v1.0.7

running Ruby 2.0

(Puma)

Passenger 4.0.37Ruby 2.0.02014.0364bit Amazon Linux 2014.03

v1.0.7

running Ruby 2.0

(Passenger Standalone)

Passenger 4.0.37Ruby 1.9.32014.0332bit Amazon Linux 2014.03

v1.0.7

running Ruby 1.9.3

Passenger 4.0.37Ruby 1.9.32014.0364bit Amazon Linux 2014.03

v1.0.7

running Ruby 1.9.3

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Ruby

Elastic Beanstalk supports the following container types for environments created with Ruby containers

between August 14, 2014 and September 23, 2014:

Ruby Container Types

Application/Web ServerLanguageAMIName

Puma 2.8.1 and Nginx

1.4.7

Ruby 2.1.22014.0364bit Amazon Linux 2014.03

v1.0.0 running Ruby 2.1

(Puma)

Passenger 4.0.37Ruby 2.1.22014.0364bit Amazon Linux 2014.03

v1.0.0 running Ruby 2.1 (Pas-

senger Standalone)

Elastic Beanstalk supports the following container types for environments created with Ruby containers

between June 30, 2014 and August 13, 2014:

Ruby Container Types

Application/Web ServerLanguageAMIName

Puma 2.8.1 and Nginx

1.4.7

Ruby 2.0.02014.0364bit Amazon Linux 2014.03

v1.0.5 running Ruby 2.0

(Puma)

Passenger 4.0.37Ruby 2.0.02014.0364bit Amazon Linux 2014.03

v1.0.4 running Ruby 2.0 (Pas-

senger Standalone)

Passenger 4.0.37Ruby 1.9.32014.0364bit Amazon Linux 2014.03

v1.0.4 running Ruby 1.9.3

Elastic Beanstalk supports the following container types for environments created with Ruby containers

between June 5, 2014 and June 29, 2014:

Ruby Container Types

Application/Web ServerLanguageAMIName

Puma 2.8.1 and Nginx

1.4.7

Ruby 2.0.02014.0364bit Amazon Linux 2014.03

v1.0.4

running Ruby 2.0

(Puma)

Passenger 4.0.37Ruby 2.0.02014.0364bit Amazon Linux 2014.03

v1.0.3

running Ruby 2.0

(Passenger Standalone)

Passenger 4.0.37Ruby 1.9.32014.0332bit Amazon Linux 2014.03

v1.0.3

running Ruby 1.9.3

Passenger 4.0.37Ruby 1.9.32014.0364bit Amazon Linux 2014.03

v1.0.3

running Ruby 1.9.3

Elastic Beanstalk supports the following container types for environments created with Ruby containers

between May 14, 2014 and June 4, 2014:

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Ruby

Ruby Container Types

Application/Web ServerLanguageAMIName

Puma 2.8.1 and Nginx

1.4.7

Ruby 2.0.02014.0364bit Amazon Linux 2014.03

v1.0.3 running Ruby 2.0

(Puma)

Elastic Beanstalk supports the following container types for environments created with Ruby containers

between May 5, 2014 and May 13, 2014:

Ruby Container Types

Application/Web ServerLanguageAMIName

Puma 2.8.1 and Nginx

1.4.7

Ruby 2.0.02014.0364bit Amazon Linux 2014.03

v1.0.2 running Ruby 2.0

(Puma)

Passenger 4.0.37Ruby 2.0.02014.0364bit Amazon Linux 2014.03

v1.0.2 running Ruby 2.0 (Pas-

senger Standalone)

Passenger 4.0.37Ruby 1.9.32014.0332bit Amazon Linux 2014.03

v1.0.2 running Ruby 1.9.3

Passenger 4.0.37Ruby 1.9.32014.0364bit Amazon Linux 2014.03

v1.0.2 running Ruby 1.9.3

Elastic Beanstalk supports the following container types for environments created with Ruby containers

between April 7, 2014 and May 4, 2014:

Ruby Container Types

Application/Web ServerLanguageAMIName

Puma 2.8.1 and Nginx

1.4.7

Ruby 2.0.02014.0364bit Amazon Linux 2014.03

v1.0.1

running Ruby 2.0

(Puma)

Passenger 4.0.37Ruby 2.0.02014.0364bit Amazon Linux 2014.03

v1.0.1

running Ruby 2.0

(Passenger Standalone)

Passenger 4.0.37Ruby 1.9.32013.0932bit Amazon Linux 2014.02

v1.0.1

running Ruby 1.9.3

Passenger 4.0.37Ruby 1.9.32013.0964bit Amazon Linux 2014.02

v1.0.1

running Ruby 1.9.3

Passenger 4.0.37Ruby 1.8.72013.0932bit Amazon Linux 2014.02

v1.0.1

running Ruby 1.8.7

Passenger 4.0.37Ruby 1.8.72013.0964bit Amazon Linux 2014.02

v1.0.1

running Ruby 1.8.7

Passenger 4.0.20Ruby 1.9.32013.0932bit Amazon Linux 2013.09

v1.0.1

running Ruby 1.9.3

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Ruby

Ruby Container Types

Passenger 4.0.20Ruby 1.9.32013.0964bit Amazon Linux 2013.09

v1.0.1

running Ruby 1.9.3

Passenger 4.0.20Ruby 1.8.72013.0932bit Amazon Linux 2013.09

v1.0.1

running Ruby 1.8.7

Passenger 4.0.20Ruby 1.8.72013.0964bit Amazon Linux 2013.09

v1.0.1

running Ruby 1.8.7

Elastic Beanstalk supports the following container types for environments created with Ruby containers

between April 2, 2014 and April 6, 2014:

Ruby Container Types

Application/Web ServerLanguageAMIName

Puma 2.8.1 and Nginx

1.4.7

Ruby 2.0.02014.0364bit Amazon Linux 2014.03

running Ruby 2.0 (Puma)

Passenger 4.0.37Ruby 2.0.02014.0364bit Amazon Linux 2014.03

running Ruby 2.0 (Passenger

Standalone)

Passenger 4.0.37Ruby 1.9.32013.0932bit Amazon Linux 2014.02

running Ruby 1.9.3

Passenger 4.0.37Ruby 1.9.32013.0964bit Amazon Linux 2014.02

running Ruby 1.9.3

Passenger 4.0.37Ruby 1.8.72013.0932bit Amazon Linux 2014.02

running Ruby 1.8.7

Passenger 4.0.37Ruby 1.8.72013.0964bit Amazon Linux 2014.02

running Ruby 1.8.7

Passenger 4.0.20Ruby 1.9.32013.0932bit Amazon Linux 2013.09

running Ruby 1.9.3

Passenger 4.0.20Ruby 1.9.32013.0964bit Amazon Linux 2013.09

running Ruby 1.9.3

Passenger 4.0.20Ruby 1.8.72013.0932bit Amazon Linux 2013.09

running Ruby 1.8.7

Passenger 4.0.20Ruby 1.8.72013.0964bit Amazon Linux 2013.09

running Ruby 1.8.7

Elastic Beanstalk supports the following container types for environments created with Ruby containers

between March 18, 2014 and April 1, 2014:

Ruby Container Types

Application/Web ServerLanguageAMIName

Passenger 4.0.37Ruby 1.9.32013.0932bit Amazon Linux 2014.02

running Ruby 1.9.3

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Ruby

Ruby Container Types

Passenger 4.0.37Ruby 1.9.32013.0964bit Amazon Linux 2014.02

running Ruby 1.9.3

Passenger 4.0.37Ruby 1.8.72013.0932bit Amazon Linux 2014.02

running Ruby 1.8.7

Passenger 4.0.37Ruby 1.8.72013.0964bit Amazon Linux 2014.02

running Ruby 1.8.7

Passenger 4.0.20Ruby 1.9.32013.0932bit Amazon Linux 2013.09

running Ruby 1.9.3

Passenger 4.0.20Ruby 1.9.32013.0964bit Amazon Linux 2013.09

running Ruby 1.9.3

Passenger 4.0.20Ruby 1.8.72013.0932bit Amazon Linux 2013.09

running Ruby 1.8.7

Passenger 4.0.20Ruby 1.8.72013.0964bit Amazon Linux 2013.09

running Ruby 1.8.7

Elastic Beanstalk supports the following container types for environments created with Ruby containers

between November 9, 2013 and March 17, 2014:

Ruby Container Types

Application/Web ServerLanguageAMIName

Passenger 4.0.20Ruby 1.9.32013.0932bit Amazon Linux 2013.09

running Ruby 1.9.3

Passenger 4.0.20Ruby 1.9.32013.0964bit Amazon Linux 2013.09

running Ruby 1.9.3

Passenger 4.0.20Ruby 1.8.72013.0932bit Amazon Linux 2013.09

running Ruby 1.8.7

Passenger 4.0.20Ruby 1.8.72013.0964bit Amazon Linux 2013.09

running Ruby 1.8.7

Elastic Beanstalk supports the following container types for environments created with Ruby containers

prior to November 9, 2013:

Ruby Container Types

Application/Web ServerLanguageAMIName

Passenger 3.0.17Ruby 1.9.32012.0932bit Amazon Linux running

Ruby 1.9.3

Passenger 3.0.17Ruby 1.9.32012.0964bit Amazon Linux running

Ruby 1.9.3

Passenger 3.0.17Ruby 1.8.72012.0932bit Amazon Linux running

Ruby 1.8.7

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Ruby

Ruby Container Types

Passenger 3.0.17Ruby 1.8.72012.0964bit Amazon Linux running

Ruby 1.8.7

Design Considerations

Because applications deployed using Elastic Beanstalk run on Amazon cloud resources, you should keep

several things in mind when designing your application: scalability, security, persistent storage, fault

tolerance, content delivery, software updates and patching, and connectivity. For a comprehensive list

of technical AWS whitepapers, covering topics such as architecture, security and economics, go to AWS

Cloud Computing Whitepapers.

Scalability

When you're operating in a physical hardware environment, as opposed to a cloud environment, you can

approach scalability two ways—you can scale up (vertical scaling) or scale out (horizontal scaling).The

scale-up approach requires an investment in powerful hardware as the demands on the business increase,

whereas the scale-out approach requires following a distributed model of investment, so hardware and

application acquisitions are more targeted, data sets are federated, and design is service-oriented. The

scale-up approach could become very expensive, and there's still the risk that demand could outgrow

capacity. Although the scale-out approach is usually more effective, it requires predicting the demand at

regular intervals and deploying infrastructure in chunks to meet demand. This approach often leads to

excessive capacity and requires constant manual monitoring.

By moving to the cloud you can bring the use of your infrastructure into close alignment with demand by

leveraging the elasticity of the cloud. Elasticity is the streamlining of resource acquisition and release, so

that your infrastructure can rapidly scale in and scale out as demand fluctuates.To implement elasticity,

configure your Auto Scaling settings to send triggers to your system to take appropriate actions based

on metrics (utilization of the servers or network I/O, for instance).You can use Auto Scaling to automatically

add compute capacity when usage rises and remove it when usage drops. Monitor your system metrics

(CPU, memory, disk I/O, network I/O) using Amazon CloudWatch so that you can take appropriate actions

(such as launching new AMIs dynamically using Auto Scaling) or send notifications. For more instructions

on configuring Auto Scaling, see Configuring Auto Scaling with Elastic Beanstalk (p. 367).

Elastic Beanstalk applications should also be as stateless as possible, using loosely coupled fault-tolerant

components that can be scaled out as needed. For more information about designing scalable application

architectures for AWS, go to Architecting for the Cloud: Best Practices.

Security

Physical security is typically handled by your service provider, however network and application-level

security is your responsibility. If you need to protect information from your clients to your elastic load

balancer, you should configure SSL.You will need a certificate from an external certification authority

such as VeriSign or Entrust. The public key included in the certificate authenticates your server to the

browser and serves as the basis for creating the shared session key used to encrypt the data in both

directions. For instructions on creating and uploading an SSL certificate, go to Creating and Uploading

Server Certificates in Using AWS Identity and Access Management. For instructions on configuring your

SSL ID for your Elastic Beanstalk application, see Ports and Cross-zone Load Balancing (p. 359).

Note

Data moving between the Elastic Load Balancer and the Amazon EC2 instances is unencrypted.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Design Considerations

Persistent Storage

Elastic Beanstalk applications run on Amazon EC2 instances that have no persistent local storage.When

the Amazon EC2 instances terminate, the local file system is not saved, and new Amazon EC2 instances

start with a default file system.You should design your application to store data in a persistent data

source. Amazon Web Services offers a number of persistent storage options that you can leverage for

your application, including:

• Amazon Simple Storage Service (Amazon S3). For more information about Amazon S3, go to the

documentation.

• Amazon Elastic Block Store (Amazon EBS). For more information, go to the documentation and see

also the article Feature Guide: Elastic Block Store.

• Amazon DynamoDB. For more information, go to the documentation. For an example using Amazon

DynamoDB with Elastic Beanstalk, see Example: DynamoDB, CloudWatch, and SNS (p. 467).

• Amazon Relational Database Service (Amazon RDS). For more information, go to the documentation

and see also Amazon RDS for C# Developers.

Fault Tolerance

As a rule of thumb, you should be a pessimist when designing architecture for the cloud. Always design,

implement, and deploy for automated recovery from failure. Use multiple Availability Zones for your

Amazon EC2 instances and for Amazon RDS. Availability Zones are conceptually like logical data centers.

Use Amazon CloudWatch to get more visibility into the health of your Elastic Beanstalk application and

take appropriate actions in case of hardware failure or performance degradation. Configure your Auto

Scaling settings to maintain your fleet of Amazon EC2 instances at a fixed size so that unhealthy Amazon

EC2 instances are replaced by new ones. If you are using Amazon RDS, then set the retention period

for backups, so that Amazon RDS can perform automated backups.

Content Delivery

When users connect to your website, their requests may be routed through a number of individual networks.

As a result users may experience poor performance due to high latency. Amazon CloudFront can help

ameliorate latency issues by distributing your web content (such as images, video, and so on) across a

network of edge locations around the world. End users are routed to the nearest edge location, so content

is delivered with the best possible performance. CloudFront works seamlessly with Amazon S3, which

durably stores the original, definitive versions of your files. For more information about Amazon CloudFront,

see http://aws.amazon.com/cloudfront.

Software Updates and Patching

Elastic Beanstalk does not currently have a software update mechanism or policy. Elastic Beanstalk

periodically updates its default AMIs with new software and patches. Running environments, however,

do not get automatically updated.To obtain the latest AMIs, you must launch a new environment. For

more information about launching a new environment, see Launching New Environments (p. 299).

Connectivity

Amazon EC2 instances require Internet connectivity to complete deployment.When you deploy an Elastic

Beanstalk application inside an Amazon VPC, the configuration required to enable Internet connectivity

depends on the type of Amazon VPC environment you create:

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Persistent Storage

• For single-instance environments, no additional configuration is required because Elastic Beanstalk

assigns each Amazon EC2 instance a public Elastic IP address that enables the instance to communicate

directly with the Internet.

• For load-balancing, autoscaling environments in an Amazon VPC with both public and private subnets,

you must do the following:

• Create a load balancer in the public subnet to route inbound traffic from the Internet to the Amazon

EC2 instances.

• Create a network address translation (NAT) instance to route outbound traffic from the Amazon EC2

instances to the Internet.

• Create inbound and outbound routing rules for the Amazon EC2 instances inside the private subnet.

• Configure the default Amazon VPC security group to allow traffic from the Amazon EC2 instances

to the NAT instance.

• For a load-balancing, autoscaling environment in an Amazon VPC that has one public subnet, no

additional configuration is required because the Amazon EC2 instances are configured with a public

IP address that enables the instances to communicate with the Internet.

For more information about using Elastic Beanstalk with Amazon VPC, see Using Elastic Beanstalk with

Amazon VPC (p. 531).

Where to Go Next

Now that you have learned some Elastic Beanstalk basics, you are ready to start creating and deploying

your applications. If you are a developer, go to one of the following sections:

• Java — Creating and Deploying Elastic Beanstalk Applications in Java Using AWS Toolkit for

Eclipse (p. 93)

• .NET — Creating and Deploying Elastic Beanstalk Applications in .NET Using AWS Toolkit for Visual

Studio (p. 125)

• Node.js — Deploying Elastic Beanstalk Applications in Node.js Using EB CLI and Git (p. 174)

• PHP — Deploying Elastic Beanstalk Applications in PHP (p. 220)

• Python — Deploying Elastic Beanstalk Applications in Python Using EB CLI and Git (p. 242)

• Ruby — Deploying Elastic Beanstalk Applications in Ruby Using EB CLI and Git (p. 262)

If you want to manage and configure your applications and environments using the AWS Management

Console, command line interface, or APIs, see Managing and Configuring Applications and Environments

Using the Console, CLI, and APIs (p. 278).

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Where to Go Next

Deploying Elastic Beanstalk

Applications from Docker

Containers

Elastic Beanstalk supports the deployment of web applications from Docker containers.With Docker

containers, you can define your own runtime environment.You can choose your own platform, programming

language, and any application dependencies (such as package managers or tools), regardless of whether

other Elastic Beanstalk container types support them. Docker containers are self-contained and include

all the configuration information and software your web application requires to run. By using Docker with

Elastic Beanstalk, you have an infrastructure that automatically handles the details of capacity provisioning,

load balancing, scaling, and application health monitoring.You can manage your web application in an

environment that supports the range of services that are integrated with Elastic Beanstalk, including but

not limited to VPC, RDS, and IAM. For more information about Docker, including how to install it, what

software it requires, and how to use Docker images to launch Docker containers, go to Docker: the Linux

container engine.

This section provides step-by-step instructions for deploying a sample web application to Elastic Beanstalk

from a Docker container.You can deploy your application in just a few minutes using eb (a command

line interface) and Git or by using the AWS Management Console. This section also explains how to

create manifest files for custom Docker images and Docker containers. For more information, see the

following topics:

• Deploying an Application from a Docker Container to Elastic Beanstalk Using the Elastic Beanstalk

Console (p. 62)

• Deploying an Application from a Docker Container to Elastic Beanstalk Using Eb (p. 63)

• Single Container Docker Configurations (p. 68)

After you deploy your Elastic Beanstalk application, you can use the AWS Management Console, CLIs,

or the APIs to manage your Elastic Beanstalk environment. For more information, see Managing and

Configuring Applications and Environments Using the Console, CLI, and APIs (p. 278).

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Deploying an Application from a Docker

Container to Elastic Beanstalk Using the Elastic

Beanstalk Console

If you prefer to use a graphical user interface to deploy your application, you can use the Elastic Beanstalk

console. During the deployment process, you can choose the sample application provided by Elastic

Beanstalk or you can upload your own Docker container with your own application. If you want to deploy

your own Docker container, see Single Container Docker Configurations (p. 68) for information about

how to properly create a customized Dockerfile, Dockerrun.aws.json, or .zip file to upload to

Elastic Beanstalk. If you prefer, you can use one of the following sample applications:

• PHP sample application

• Python sample application

For examples, you can refer to the Dockerfile included with the PHP sample application.The Python

application also includes an example Dockerfile. It also includes a Dockerrun.aws.json file that is

unique to Elastic Beanstalk. For more information about the Dockerfile and Dockerrun.aws.json

file, see Single Container Docker Configurations (p. 68).

The PHP sample application uses Amazon RDS, and the Python sample application uses Amazon

DynamoDB, Amazon SQS, and Amazon SNS.You may be charged for using these services. If you are

a new customer, you can make use of the AWS Free Usage Tier. For more information about pricing,

see the following:

• Amazon Relational Database Service (RDS) Pricing

• Amazon DynamoDB Pricing

• Amazon SQS Pricing

• Amazon SNS Pricing

If you want Elastic Beanstalk to run the game 2048, you can upload the following Dockerfile as written.

FROM ubuntu:12.04

RUN apt-get update

RUN apt-get install -y nginx zip curl

RUN echo "daemon off;" >> /etc/nginx/nginx.conf

RUN curl -o /usr/share/nginx/www/master.zip -L https://codeload.github.com/gab

rielecirulli/2048/zip/master

RUN cd /usr/share/nginx/www/ && unzip master.zip && mv 2048-master/* . && rm -

rf 2048-master master.zip

EXPOSE 80

CMD ["/usr/sbin/nginx", "-c", "/etc/nginx/nginx.conf"]

To deploy your application from a Docker container using the Elastic Beanstalk console

1. Using the Elastic Beanstalk console, create a new application with any of the following. For detailed

instructions, see Creating New Applications (p. 279).

• The sample application included with the console

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Single Container Docker Using the Console

• One of the previously described sample applications

• The sample Dockerfile

• Your own Dockerfile

• Your own Dockerrun.aws.json file

• Your own .zip file

2. Once your environment is green and ready, click the URL link on the environment dashboard to view

your application.

Because your application will be live, you should consider creating multiple environments, such as a

testing environment and a production environment.You can point your domain name to an Amazon Route

53 (a highly available and scalable Domain Name System [DNS] web service) CNAME, such as

<yourappname>.elasticbeanstalk.com. For information about how to map your root domain to your Elastic

Load Balancer, see Using Elastic Beanstalk with Amazon Route 53 to Map Your Domain to Your Load

Balancer (p. 528).

Deploying an Application from a Docker

Container to Elastic Beanstalk Using Eb

You can use the eb command line tool and Git to deploy an application. Eb is a command line interface

that helps you to deploy applications quickly and more easily using Git. Eb is available as part of the

Elastic Beanstalk command line tools package. If you prefer to use a graphical user interface, you can

use the AWS Management Console. For more information, see Deploying an Application from a Docker

Container to Elastic Beanstalk Using the Elastic Beanstalk Console (p. 62).You can follow these

procedures to upload a sample application or your own Docker container with your own application. If

you want to deploy your own Docker container, first see Single Container Docker Configurations (p. 68)

for information about how to properly create a customized Dockerfile, Dockerrun.aws.json, or

.zip file to upload to Elastic Beanstalk.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Single Container Docker Using Eb

Set Up Eb

Use the following steps to install eb and initialize your Git repository. The command line tools package

has two versions. Install version 2.6.1.

To install eb, its prerequisite software, and initialize your Git repository

1. Install the following software onto your local computer:

• Linux/Unix/Mac

• Elastic Beanstalk command line tools package, version 2.6.1, available in .zip format from

the AWS Sample Code & Libraries website

• Git 1.6.6 or later, available from http://git-scm.com/

• Python 2.7 or 3.0

Windows

• Elastic Beanstalk command line tools package, version 2.6.1, available in .zip format from

the AWS Sample Code & Libraries website

• Git 1.6.6 or later, available from http://git-scm.com/

• PowerShell 2.0

Note

Windows 7 and Windows Server 2008 R2 come with PowerShell 2.0. If you are

running an earlier version of Windows, you can download PowerShell 2.0. For more

information, go to the Windows PowerShell Scripting pages.

2. Initialize your Git repository.

git init .

After installing eb on your local computer, use the Git command line to create your local repository and

add and commit changes. Create your application as you normally would with your favorite editor. If you

prefer, you can use one of the following sample applications:

• PHP sample application

• Python sample application

For examples, you can refer to the Dockerfile included with the PHP sample application.The Python

application also includes a Dockerfile example. It also includes a Dockerrun.aws.json file that is

unique to Elastic Beanstalk. For more information about the Dockerfile and Dockerrun.aws.json

file, see Single Container Docker Configurations (p. 68).

The PHP sample application uses Amazon RDS, and the Python sample application uses Amazon

DynamoDB, Amazon SQS, and Amazon SNS.You may be charged for using these services. If you are

a new customer, you can make use of the AWS Free Usage Tier. For more information about pricing,

see the following:

• Amazon Relational Database Service (RDS) Pricing

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Set Up Eb

• Amazon DynamoDB Pricing

• Amazon SQS Pricing

• Amazon SNS Pricing

If you want Elastic Beanstalk to run the game 2048, you can upload the following Dockerfile as written.

FROM ubuntu:12.04

RUN apt-get update

RUN apt-get install -y nginx zip curl

RUN echo "daemon off;" >> /etc/nginx/nginx.conf

RUN curl -o /usr/share/nginx/www/master.zip -L https://codeload.github.com/gab

rielecirulli/2048/zip/master

RUN cd /usr/share/nginx/www/ && unzip master.zip && mv 2048-master/* . && rm -

rf 2048-master master.zip

EXPOSE 80

CMD ["/usr/sbin/nginx", "-c", "/etc/nginx/nginx.conf"]

Next, create a new local repository, add your new program, and commit your change.

git add <filename>

git commit -m "initial check-in"

Note

For information about Git commands, go to Git - Fast Version Control System.

Before you use eb, set your PATH to the location of eb. The following table shows an example for

Linux/UNIX and Windows.

In WindowsIn Linux and UNIX

C:\> set PATH=%PATH%;<path to unzipped

eb CLI package>\eb\windows\

$ export PATH=$PATH:<path to unzipped

eb CLI package>/eb/linux/python2.7/

If you are using Python 3.0, the path will include

python3 rather than python2.7.

Use the init command, and Elastic Beanstalk will prompt you to enter this information. If a default value

is available, and you want to use it, press Enter.

Because your application will be live, you should consider creating multiple environments, such as a

testing environment and a production environment.You can point your domain name to an Amazon Route

53 (a highly available and scalable Domain Name System [DNS] web service) CNAME, such as

<yourappname>.elasticbeanstalk.com. For information about how to map your root domain to your Elastic

Load Balancer, see Using Elastic Beanstalk with Amazon Route 53 to Map Your Domain to Your Load

Balancer (p. 528).

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Set Up Eb

Configure Elastic Beanstalk Using Eb

To configure Elastic Beanstalk

1. From the directory where you created your local repository, type the following command:

eb init

2. When you are prompted for the access key ID, type your access key ID.To get your access key ID,

see How Do I Get Security Credentials? in the AWS General Reference.

Enter your AWS Access Key ID (current value is "AKIAIOSFODNN7EXAMPLE"):

3. When you are prompted for the secret access key, type your secret access key.To get your secret

access key, see How Do I Get Security Credentials? in the AWS General Reference.

Enter your AWS Secret Access Key (current value is "wJalrXUtnFEMI/K7MDENG/bPxR

fiCYEXAMPLEKEY"):

4. When you are prompted for the Elastic Beanstalk region, type the number of the region. For information

about this product's regions, go to Regions and Endpoints in the Amazon Web Services General

Reference. For this example, we'll use US West (Oregon).

5. When you are prompted for the Elastic Beanstalk application name, type the name of the application.

Elastic Beanstalk generates an application name based on the current directory name if an application

name has not been previously configured. In this example, we use dockerapp.

Enter an AWS Elastic Beanstalk application name (auto-generated value is

"windows"): dockerapp

Note

If you have a space in your application name, make sure you do not use quotation marks.

6. When you are prompted for the Elastic Beanstalk environment name, type the name of the

environment. Elastic Beanstalk automatically creates an environment name based on your application

name. If you want to accept the default, press Enter.

Enter an AWS Elastic Beanstalk environment name (current value is "windows-

env"): dockerapp-env

Note

If you have a space in your application name, make sure you do not have a space in your

environment name.

7. When you are prompted, choose an environment tier. For more information about environment tiers,

see Architectural Overview (p. 16). For this example, we'll use 1.

Available environment tiers are:

1) WebServer::Standard::1.0

2) Worker::SQS/HTTP::1.0

8. When you are prompted for the solution stack, type the number of the solution stack you want. For

this example, we'll use 64bit Amazon Linux 2014.03 v1.0.2 running Docker 0.9.0.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Configure Elastic Beanstalk Using Eb

9. When you are prompted, choose an environment type. In this example, we'll use 2.

Available environment types are:

1) LoadBalanced

2) SingleInstance

10. When you are prompted to create an Amazon RDS DB instance, type y or n. For this example, we'll

type n.

Create an RDS DB Instance? [y/n]:

11. When you are prompted to enter your instance profile name, you can choose to create a default

instance profile or use an existing instance profile. Using an instance profile enables IAM users and

AWS services to gain access to temporary security credentials to make AWS API calls. Using instance

profiles prevents you from having to store long-term security credentials on the EC2 instance. For

more information about instance profiles, see Granting Permissions to Users and Services Using

IAM Roles (p. 562). For this example, we'll use Create a default instance profile.

You should see a confirmation that your AWS Credential file was successfully updated.

After configuring Elastic Beanstalk, you are ready to create and deploy an application.

Create an Application

Next, you need to create and deploy a sample application. For this step, you use a sample application

that is already prepared. Elastic Beanstalk uses the configuration information you specified in the previous

step to do the following:

• Create an application using the application name you specified.

• Launch an environment using the environment name you specified that provisions the AWS resources

to host the application.

• Deploy the application into the newly created environment.

Use the start command to create and deploy a sample application.

To create the application

• From the directory where you created your local repository, type the following command:

eb start

It may take several minutes to complete this process. Elastic Beanstalk provides status updates during

the process. If at any time you want to stop polling for status updates, press Ctrl+C.When the environment

status is Green, Elastic Beanstalk outputs a URL for the application.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Create an Application

Single Container Docker Configurations

This section describes how to prepare your Docker image and container for uploading to Elastic Beanstalk.

Any web application that you deploy to Elastic Beanstalk in single-container Docker container must include

a Dockerfile, which defines a custom image, a Dockerrun.aws.json file, which specifies an existing

image to use and environment configuration, or both.You can deploy your web application from a Docker

container to Elastic Beanstalk by doing one of the following:

• Create a Dockerfile customize an image and to deploy a Docker container to Elastic Beanstalk.

• Create a Dockerrun.aws.json file to deploy a Docker container from an existing Docker image to

Elastic Beanstalk.

• Create a .zip file containing your application files, any application file dependencies, the Dockerfile,

and the Dockerrun.aws.json file.

Note

If you use only a Dockerfile or only a Dockerrun.aws.json file to deploy your application,

you do not need to compress the file into a .zip file.

Dockerfile

Docker uses a Dockerfile to create a Docker image that contains your source bundle. A Docker image

is the template from which you create a Docker container. Dockerfile is a plain text file that contains

instructions that Elastic Beanstalk uses to build a customized Docker image on each Amazon EC2 instance

in your Elastic Beanstalk environment. Create a Dockerfile when you do not already have an existing

image hosted in a repository.

Include the following instructions in the Dockerfile:

• FROM – (required as the first instruction in the file) Specifies the base image from which to build the

Docker container and against which Elastic Beanstalk runs subsequent Dockerfile instructions.

The image can be hosted in a public repository, a private repository hosted by a third-party registry, or

a repository that you run on EC2.

• EXPOSE – (required) Lists the ports to expose on the Docker container. Elastic Beanstalk uses the

port value to connect the Docker container to the reverse proxy running on the host.

You can specify multiple container ports, but Elastic Beanstalk uses only the first one to connect your

container to the host's reverse proxy and route requests from the public Internet.

• CMD – Specifies an executable and default parameters, which are combined into the command that

the container runs at launch. Use the following format:

CMD ["executable","param1","param2"]

CMD can also be used to provide default parameters for an ENTRYPOINT command by omitting the

executable argument. An executable must be specified in either a CMD or an ENTRYPOINT, but not

both. For basic scenarios, use a CMD and omit the ENTRYPOINT.

• ENTRYPOINT – Uses the same JSON format as CMD and, like CMD, specifies a command to run when

the container is launched. Also allows a container to be run as an executable with docker run.

If you define an ENTRYPOINT, you can use a CMD as well to specify default parameters that can be

overridden with docker run's -d option. The command defined by an ENTRYPOINT (including any

parameters) is combined with parameters from CMD or docker run when the container is run.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Single Container Docker Configurations

• RUN – Specifies one or more commands that install packages and configure your web application

inside the image.

If you include RUN instructions in the Dockerfile, compress the file and the context used by RUN

instructions in the Dockerfile into a .zip file. Compress files at the top level of the directory.

Note

To use a private repository hosted by a third-party registry, you must provide a JSON file called

.dockercfg with information required to authenticate with the repository.Your authentication

credentials are written to a .dockercfg file when you run the command $ sudo docker

docker login server_name.) Declare the .dockercfg file in the Dockerrun.aws.json

file. Make sure that the .dockercfg file contains a valid Amazon S3 bucket and Amazon EC2

key pair.The Amazon S3 bucket must be hosted in the same region.as the environment that is

using it. Elastic Beanstalk will not download files from Amazon S3 buckets hosted in other regions.

Grant permissions for the action s3:GetObject to the IAM role in the instance profile. For an

example policy, see Using IAM Roles with Elastic Beanstalk (p.568). For more information about

the .dockercfg file, go to Working with Docker Hub on the Docker website.

The following snippet is an example of the Dockerfile. When you follow the instructions in Deploying

an Application from a Docker Container to Elastic Beanstalk Using the Elastic Beanstalk Console (p. 62),

you can upload this Dockerfile as written. Elastic Beanstalk runs the game 2048 when you use this

Dockerfile.

FROM ubuntu:12.04

RUN apt-get update

RUN apt-get install -y nginx zip curl

RUN echo "daemon off;" >> /etc/nginx/nginx.conf

RUN curl -o /usr/share/nginx/www/master.zip -L https://codeload.github.com/gab

rielecirulli/2048/zip/master

RUN cd /usr/share/nginx/www/ && unzip master.zip && mv 2048-master/* . && rm -

rf 2048-master master.zip

EXPOSE 80

CMD ["/usr/sbin/nginx", "-c", "/etc/nginx/nginx.conf"]

For more information about instructions you can include in the Dockerfile, go to Dockerfile Reference

on the Docker website.

Dockerrun.aws.json

A Dockerrun.aws.json file describes how to deploy a Docker container as an Elastic Beanstalk

application.This JSON file is specific to Elastic Beanstalk. If your application runs on an image that is

available in a hosted repository, you can specify the image in a Dockerrun.aws.json file and omit the

Dockerfile.

Valid keys and values for the Dockerrun.aws.json file include the following:

• AWSEBDockerrunVersion – (required) Specifies the version number as the value "1" for Single

Container Docker environments

• Authentication – (required only for private repositories) Specifies the Amazon S3 object storing the

.dockercfg file.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Dockerrun.aws.json

• Image – Specifies the Docker base image on an existing Docker repository from which you're building

a Docker container. Specify the value of the Name key in the format <organization>/<image

name> for images on Docker Hub, or <site>/<organization name>/<image name> for other

sites.

When you specify an image in the Dockerrun.aws.json file, each instance in your Elastic Beanstalk

environment will run docker pull on that image and run it. Optionally include the Update key. The

default value is "true" and instructs Elastic Beanstalk to check the repository, pull any updates to the

image, and overwrite any cached images.

Do not specify the Image key in the Dockerrun.aws.json file when using a Dockerfile. .Elastic

Beanstalk will always build and use the image described in the Dockerfile when one is present.

• Ports – (required when you specify the Image key) Lists the ports to expose on the Docker container.

Elastic Beanstalk uses ContainerPort value to connect the Docker container to the reverse proxy

running on the host.

You can specify multiple container ports, but Elastic Beanstalk uses only the first one to connect your

container to the host's reverse proxy and route requests from the public Internet.

• Volumes – Maps volumes from an EC2 instance to your Docker container. Specify one or more arrays

of volumes to map.

• Logging – Maps the log directory inside the container.

Configure Elastic Beanstalk to publish log files for the Docker container or to view snapshot logs. For

more information, see Working with Logs (p. 415).

The following snippet is an example that illustrates the syntax of the Dockerrun.aws.json file for a

single container.

{

"AWSEBDockerrunVersion": "1",

"Image": {

"Name": "janedoe/image",

"Update": "true"

"Ports": [

{

"ContainerPort": "1234"

}

"Volumes": [

{

"HostDirectory": "/var/app/mydb",

"ContainerDirectory": "/etc/mysql"

}

"Logging": "/var/log/nginx"

}

Note

The previous example specifies an image on a public repository. The following example snippet

illustrates how to use the Image key to specify an image in a private repository hosted by the

third-party registry www.quay.io.

{

"AWSEBDockerrunVersion": "1",

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Dockerrun.aws.json

"Authentication": {

"Bucket": "my-bucket",

"Key": "mydockercfg"

"Image": {

"Name": "quay.io/johndoe/image-test",

"Update": "true"

"Ports": [

{

"ContainerPort": "1234"

}

"Volumes": [

{

"HostDirectory": "/var/app/mydb",

"ContainerDirectory": "/etc/mysql"

}

"Logging": "/var/log/nginx"

}

You can provide Elastic Beanstalk with only the Dockerrun.aws.json file or in addition to the

Dockerfile in a .zip file.When you provide both files, the Dockerfile builds the Docker image and

the Dockerrun.aws.json file provides additional information for deployment as described later in this

section.When you provide both the Dockerfile and the Dockerrun.aws.json file, do not specify an

image in the Dockerrun.aws.json file. Elastic Beanstalk uses the image specified in the Dockerfile

and ignores it in the Dockerrun.aws.json file.

Multicontainer Docker Environments

You can create docker environments that support multiple containers per instance with multicontainer

Docker platform for Elastic Beanstalk.

Elastic Beanstalk uses Amazon EC2 Container Service to coordinate container deployments to

multicontainer Docker environments. Amazon ECS provides tools to manage a cluster of instances running

Docker containers. Elastic Beanstalk takes care of Amazon ECS tasks including cluster creation, task

definition and execution.

Topics

• Multicontainer Docker Platform (p. 71)

• Dockerrun.aws.json File (p. 72)

• Docker Images (p. 72)

• Container Instance Role (p. 73)

• Amazon ECS Resources Created by Elastic Beanstalk (p. 73)

• Using Multiple Elastic Load Balancing Listeners (p. 74)

Multicontainer Docker Platform

Standard generic and preconfigured Docker platforms on Elastic Beanstalk support only a single Docker

container per Elastic Beanstalk environment. In order to get the most out of Docker, Elastic Beanstalk

lets you create an environment where your instances run multiple Docker containers side by side.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Multicontainer Docker Environments

The following diagram shows an example Elastic Beanstalk environment configured with three Docker

containers running on each EC2 instance in an Auto Scaling group:

Dockerrun.aws.json File

Multicontainer Docker instances on Elastic Beanstalk require a configuration file named

Dockerrun.aws.json.This file is specific to Elastic Beanstalk and can be used alone or combined with

source code and content in a source bundle (p. 294) to create an environment on a Docker platform.

Note

Version 1 of the Dockerrun.aws.json format is used to launch a single Docker container to

an Elastic Beanstalk environment.Version 2 adds support for multiple containers per instance

and can only be used with the multicontainer Docker platform. The format differs significantly

from the previous version which is detailed under Single Container Docker Configurations (p. 68)

See Dockerrun.aws.json Format (p. 75) for details on the updated format and an example file.

Docker Images

The Multicontainer Docker platform for Elastic Beanstalk requires images to be prebuilt and stored in a

public or private online image repository.

Note

Building custom images during deployment with a Dockerfile is not supported by the

multicontainer Docker platform on Elastic Beanstalk. Build your images and deploy them to an

online repository before creating an Elastic Beanstalk environment.

Specify images by name in Dockerrun.aws.json. Note these conventions:

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Dockerrun.aws.json File

• Images in official repositories on Docker Hub use a single name (for example, ubuntu or mongo).

• Images in other repositories on Docker Hub are qualified with an organization name (for example,

amazon/amazon-ecs-agent).

• Images in other online repositories are qualified further by a domain name (for example,

quay.io/assemblyline/ubuntu).

To configure Elastic Beanstalk to authenticate to a private repository, include the authentication

parameter in your Dockerrun.aws.json file.

Container Instance Role

Elastic Beanstalk uses an Amazon ECS-optimized AMI with an Amazon ECS container agent that runs

in a Docker container.The agent communicates with Amazon ECS to coordinate container deployments.

In order to communicate with Amazon ECS, each instance must have the corresponding permissions in

IAM.The following IAM role provides an example:

{

"Version": "2012-10-17",

"Statement": [

{

"Effect": "Allow",

"Action": [

"ecs:StartTask",

"ecs:StopTask",

"ecs:RegisterContainerInstance",

"ecs:DeregisterContainerInstance",

"ecs:DiscoverPollEndpoint",

"ecs:Submit*",

"ecs:Poll"

"Resource": ["*"]

{

"Effect": "Allow",

"Action": "s3:PutObject",

"Resource": "arn:aws:s3:::elasticbeanstalk-*/resources/environments/logs/*"

}

]

}

For instructions on creating policies and roles in IAM, see Creating IAM Roles in the IAM User Guide.

Note

If you use a role with permissions configured for worker environment tiers, add the container

instance permissions to your existing role policy and use that.Worker environment permissions

are detailed under IAM Roles for Elastic Beanstalk Environment Tiers (p. 617).

Amazon ECS Resources Created by Elastic

Beanstalk

When you create an environment using the multicontainer Docker platform, Elastic Beanstalk automatically

creates and configures several Amazon EC2 Container Service resources while building the environment

in order to create the necessary containers on each EC2 instance.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Container Instance Role

• Amazon ECS Cluster – Container instances in Amazon ECS are organized into clusters.When used

with Elastic Beanstalk, one cluster is always created for each multicontainer Docker environment.

• Amazon ECS Task Definition – Elastic Beanstalk uses the Dockerrun.aws.json file in your project

to generate the Amazon ECS task definition that is used to configure container instances in the

environment.

• Amazon ECS Task – Elastic Beanstalk communicates with Amazon ECS to run a task on every instance

in the environment to coordinate container deployment. In an autoscaling environment, Elastic Beanstalk

initiates a new task whenever an instance is added to the cluster.

• Amazon ECS Container Agent – The agent runs in a Docker container on the instances in your

environment.The agent polls the Amazon ECS service and waits for a task to run.

• Amazon ECS Data Volumes – Elastic Beanstalk inserts volume definitions (in addition to the volumes

that you define in Dockerrun.aws.json) into the task definition to facilitate log collection.

Elastic Beanstalk creates log volumes on the container instance, one for each container, at

/var/log/containers/containername.These volumes are named awseb-logs-containername

and are provided for containers to mount. See Container Definition Format (p. 77) for details on how

to mount them.

Using Multiple Elastic Load Balancing Listeners

You can configure multiple Elastic Load Balancing listeners on a multicontainer Docker environment in

order to support inbound traffic for proxies or other services that don't run on the default HTTP port.

Create a .ebextensions folder in your source bundle and add a file with a .config file extension.The

following example shows a configuration file that creates an Elastic Load Balancing listener on port 8080

and opens the same port for inbound traffic on the Elastic Beanstalk environment's security group.

.ebextensions/elb-listeners.config

option_settings:

aws:elb:listener:8080:

ListenerProtocol: HTTP

InstanceProtocol: HTTP

InstancePort: 8080

Resources:

port8080SecurityGroupIngress:

Type: AWS::EC2::SecurityGroupIngress

Properties:

GroupName: {Ref : AWSEBSecurityGroup}

IpProtocol: tcp

ToPort: 8080

FromPort: 8080

SourceSecurityGroupName: { "Fn::GetAtt": ["AWSEBLoadBalancer",

"SourceSecurityGroup.GroupName"] }

SourceSecurityGroupOwnerId: { "Fn::GetAtt": ["AWSEBLoadBalancer",

"SourceSecurityGroup.OwnerAlias"] }

For more information on the configuration file format, see Customizing Environment Resources (p. 456)

and Option_settings (p. 440)

In addition to adding a listener to the Elastic Load Balancing configuration and opening a port in the

security group, you need to map the port on the host instance to a port on the Docker container in the

containerDefinitions section of the Dockerrun.aws.json file.The following excerpt shows an

example:

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Using Multiple Elastic Load Balancing Listeners

"portMappings": [

{

"hostPort": 8080,

"containerPort": 8080

}

]

See Dockerrun.aws.json Format (p. 75) for details on the Dockerrun.aws.json file format.

Multicontainer Docker Configuration

A Dockerrun.aws.json file is an Elastic Beanstalk–specific JSON file that describes how to deploy a

set of Docker containers as an Elastic Beanstalk application.You can use a Dockerrun.aws.json file

for a multicontainer Docker environment.

Dockerrun.aws.json describes the containers to deploy to each container instance in the environment

as well as the data volumes to create on the host instance for the containers to mount.

A Dockerrun.aws.json file can be used on its own or zipped up with additional source code in a single

archive. Source code that is archived with a Dockerrun.aws.json is deployed to container instances

and accessible in the /var/app/current/ directory. Use the volumes section of the config to provide

mount points for the containers running on the instance, and the mountPoints section of the embedded

container descriptions to mount them from the containers.

Topics

• Dockerrun.aws.json Format (p. 75)

Dockerrun.aws.json Format

Dockerrun.aws.json file includes three sections:

• AWSEBDockerrunVersion – Specifies the version number as the value "2" for multicontainer Docker

environments.

• containerDescriptions – An array of container definitions, detailed below.

• volumes – Creates mount points in the container instance that a container can use. Configure volumes

for folders in your source bundle (deployed to /var/app/current on the container instance) for a

container's application to read.

Note

Elastic Beanstalk configures additional volumes for logs, one for each container.These should

be mounted by your containers in order to write logs to the host instance. See Container

Definition Format (p. 77) for details.

Volumes are specified in the following format:

"volumes": [

{

"name": "volumename",

"host": {

"sourcePath": "/path/on/host/instance"

}

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Multicontainer Docker Configuration

• authentication (optional) – the location in Amazon S3 of a dockercfg file that contains authentication

data for a private repository. Uses the following format:

"authentication": {

"bucket": "my-bucket",

"key": "mydockercfg"

The following snippet is an example that illustrates the syntax of the Dockerrun.aws.json file for an

instance with two containers.

{

"AWSEBDockerrunVersion": 2,

"volumes": [

{

"name": "php-app",

"host": {

"sourcePath": "/var/app/current/php-app"

}

{

"name": "nginx-proxy-conf",

"host": {

"sourcePath": "/var/app/current/proxy/conf.d"

}

"containerDefinitions": [

{

"name": "php-app",

"image": "php:fpm",

"essential": true,

"memory": 128,

"mountPoints": [

{

"sourceVolume": "php-app",

"containerPath": "/var/www/html",

"readOnly": true

}

]

{

"name": "nginx-proxy",

"image": "nginx",

"essential": true,

"memory": 128,

"portMappings": [

{

"hostPort": 80,

"containerPort": 80

}

"links": [

"php-app"

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Dockerrun.aws.json Format

"mountPoints": [

{

"sourceVolume": "php-app",

"containerPath": "/var/www/html",

"readOnly": true

{

"sourceVolume": "nginx-proxy-conf",

"containerPath": "/etc/nginx/conf.d",

"readOnly": true

{

"sourceVolume": "awseb-logs-nginx-proxy",

"containerPath": "/var/log/nginx"

}

]

}

]

}

Container Definition Format

A Dockerrun.aws.json file contains an array of one or more container definition objects with the

following fields:

name

The name of the container.

image

The name of a Docker image in an online Docker repository from which you're building a Docker

container. Note these conventions:

• Images in official repositories on Docker Hub use a single name (for example, ubuntu or mongo).

• Images in other repositories on Docker Hub are qualified with an organization name (for example,

amazon/amazon-ecs-agent.

• Images in other online repositories are qualified further by a domain name (for example,

quay.io/assemblyline/ubuntu).

essential

True if the task should stop if the container fails. Nonessential containers can finish or crash without

affecting the rest of the containers on the instance.

memory

Amount of memory on the container instance to reserve for the container.

mountPoints

Volumes from the container instance to mount and the location on the container file system at which

to mount them. Mount volumes containing application content so your container can read the data

you upload in your source bundle, as well as log volumes for writing log data to a location where

Elastic Beanstalk can gather it.

Elastic Beanstalk creates log volumes on the container instance, one for each container, at

/var/log/containers/containername.These volumes are named

awseb-logs-containername and should be mounted to the location within the container file

structure where logs are written.

For example, the following mount point maps the Nginx log location in the container to the Elastic

Beanstalk–generated volume for the nginx-proxy container.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Dockerrun.aws.json Format

{

"sourceVolume": "awseb-logs-nginx-proxy",

"containerPath": "/var/log/nginx"

}

portMappings

Maps network ports on the container to ports on the host.

links

List of containers to link to. Linked containers can discover each other and communicate securely.

Note

The container definition and volumes sections of Dockerrun.aws.json use the same formatting

as the corresponding sections of an Amazon ECS task definition file. For more information, see

Amazon ECS Task Definitions in the Amazon ECS Developer Guide.

Multicontainer Docker Environments with the

AWS Management Console

You can launch a cluster of multicontainer instances in a single-instance or autoscaling Elastic Beanstalk

environment using the AWS Management Console.This tutorial details IAM role creation, container

configuration, and source code for an environment that uses two containers.

The containers, a PHP application and an Nginx proxy, run side by side on each of the Amazon EC2

instances in an Elastic Beanstalk environment. After creating the environment and verifying that the

applications are running, you'll connect to a container instance to see how it all fits together.

Note

This tutorial was developed using Windows 7 and Google Chrome 41.

Topics

• Configure a Container Instance IAM Role (p. 78)

• Define Docker Containers (p. 80)

• Add Content (p. 82)

• Deploy to Elastic Beanstalk (p. 82)

• Connect to a Container Instance (p. 83)

• Inspect the Amazon ECS Container Agent (p. 85)

Configure a Container Instance IAM Role

Instances in a multicontainer Docker environment must have an instance profile with permission to access

the Amazon EC2 Container Service, the service that Elastic Beanstalk uses to coordinate container

deployments.To grant Amazon ECS access to the instances in your environment, first create an IAM

policy and assign it to a role.

To create a container instance role in IAM

1. Sign in to the AWS Management Console and open the IAM console at https://

console.aws.amazon.com/iam/.

2. Click Policies, click Get Started if the welcome page appears, and then click Create Policy.

3. For Create Your Own Policy, click Select.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Tutorial - Multicontainer Docker

4. Type BeanstalkECSAccess for the policy name and Allow container instances in an

Elastic Beanstalk environment to run tasks from Amazon ECS and write logs

to S3. for the description.

5. Copy and paste the following text into the policy document:

{

"Version": "2012-10-17",

"Statement": [

{

"Effect": "Allow",

"Action": [

"ecs:StartTask",

"ecs:StopTask",

"ecs:RegisterContainerInstance",

"ecs:DeregisterContainerInstance",

"ecs:DiscoverPollEndpoint",

"ecs:Submit*",

"ecs:Poll"

"Resource": ["*"]

{

"Effect": "Allow",

"Action": "s3:PutObject",

"Resource": "arn:aws:s3:::elasticbeanstalk-*/resources/environ

ments/logs/*"

}

]

}

6. Click Create Policy

Next you will need a role to attach the policy to. If you've used Elastic Beanstalk before, you will already

have a role named aws-elasticbeanstalk-ec2-role. If not, create a new one.

To create a new role

1. While still in the IAM console, click Roles.

2. Click Create New Role.

3. Type aws-elasticbeanstalk-ec2-role for the Role Name and click Next Step.

4. Under AWS Service Roles click Select next to Amazon EC2.

5. Click Next Step.

6. Click Create Role.

Finally, assign the policy to the role.

To assign the policy to a role

1. While still in the IAM console, click Roles.

2. Click aws-elasticbeanstalk-ec2-role.

3. Click Attach Policy under Permissions.

4. Select the BeanstalkECSAccess policy and click Attach Policy.

5. Click Create Role.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Configure a Container Instance IAM Role

Define Docker Containers

The first step in creating a new Docker environment is to create a directory for your application data.This

folder can be located anywhere on your local machine and have any name you choose. In addition to a

container configuration file, this folder will contain the content that you will upload to Elastic Beanstalk

and deploy to your environment.

Note

All of the code for this tutorial is available in the awslabs repository on GitHub at

https://github.com/awslabs/eb-docker-nginx-proxy

The file that Elastic Beanstalk uses to configure the containers on an EC2 instance is a JSON-formatted

text file named Dockerrun.aws.json. Create a text file with this name at the root of your application

and add the following text:

{

"AWSEBDockerrunVersion": 2,

"volumes": [

{

"name": "php-app",

"host": {

"sourcePath": "/var/app/current/php-app"

}

{

"name": "nginx-proxy-conf",

"host": {

"sourcePath": "/var/app/current/proxy/conf.d"

}

"containerDefinitions": [

{

"name": "php-app",

"image": "php:fpm",

"essential": true,

"memory": 128,

"mountPoints": [

{

"sourceVolume": "php-app",

"containerPath": "/var/www/html",

"readOnly": true

}

]

{

"name": "nginx-proxy",

"image": "nginx",

"essential": true,

"memory": 128,

"portMappings": [

{

"hostPort": 80,

"containerPort": 80

}

"links": [

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Define Docker Containers

"php-app"

"mountPoints": [

{

"sourceVolume": "php-app",

"containerPath": "/var/www/html",

"readOnly": true

{

"sourceVolume": "nginx-proxy-conf",

"containerPath": "/etc/nginx/conf.d",

"readOnly": true

{

"sourceVolume": "awseb-logs-nginx-proxy",

"containerPath": "/var/log/nginx"

}

]

}

]

}

This example configuration defines two containers, a PHP web site with an Nginx proxy in front of it.

These two containers will run side by side in Docker containers on each instance in your Elastic Beanstalk

environment, accessing shared content (the content of the website) from volumes on the host instance,

which are also defined in this file.The containers themselves are created from images hosted in official

repositories on Docker Hub. The resulting environment looks like this:

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Define Docker Containers

The volumes defined in the configuration correspond to the content that you will create next and upload

as part of your application source bundle.The containers access content on the host by mounting volumes

in the mountPoints section of the container definitions.

For more information on the format of Dockerrun.aws.config and its parameters, see Container

Definition Format (p. 77).

Add Content

Next you will add some content for your PHP site to display to visitors, and a configuration file for the

Nginx proxy.

php-app\index.php

<h1>Hello World!!!</h1>

<h3>PHP Version <pre><?= phpversion()?></pre></h3>

php-app\static.html

<h1>Hello World!</h1>

<h3>This is a static HTML page.</h3>

proxy\conf.d\default.conf

server {

listen 80;

server_name localhost;

root /var/www/html;

index index.php;

location ~ [^/]\.php(/|$) {

fastcgi_split_path_info ^(.+?\.php)(/.*)$;

if (!-f $document_root$fastcgi_script_name) {

return 404;

}

include fastcgi_params;

fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

fastcgi_param PATH_INFO $fastcgi_path_info;

fastcgi_param PATH_TRANSLATED $document_root$fastcgi_path_info;

fastcgi_pass php-app:9000;

fastcgi_index index.php;

}

Deploy to Elastic Beanstalk

Your application folder now contains the following files:

php-app\index.php

php-app\static.html

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Add Content

proxy\conf.d\default.conf

Dockerrun.aws.json

This is all you need to create the Elastic Beanstalk environment. Create a .zip archive of the above files

and folders (not including the top-level project folder).To create the archive in Windows explorer, select

the contents of the project folder, right-click, select Send To, and then click Compressed (zipped) Folder

Note

For information on the required file structure and instructions for creating archives in other

environments, see Creating an Application Source Bundle (p. 294)

Next, you'll upload the source bundle to Elastic Beanstalk and create your environment.

To create a multicontainer Elastic Beanstalk environment

1. Sign in to the AWS Management Console and open the Elastic Beanstalk console at https://

console.aws.amazon.com/elasticbeanstalk/.

2. Click Create New Application.

3. Enter a name and description and click Next.

4. Click Create web server.

5. Select aws-elasticbeanstalk-ec2-role and click Next.

6. Set Predefined configuration to Multi-container Docker.

7. Set Environment type to Single instance and click Next.

8. For Application Version, select Upload your own.

9. Click Browse, select the .zip archive and click Open. Click Next

10. Configure your environment's name and prefix and click Next.

11. For Additional Resources, if your account does not have a default VPC, select Create this

environment inside a VPC.

Note

Multicontainer Docker environments must be launched in a VPC. Elastic Beanstalk will use

the default VPC, but you must select this option if you do not have a default VPC. AWS

accounts created after November 2013 have a default VPC. For more information, see

Your Default VPC and Subnets in the Amazon VPC User Guide.

12. On the Configuration Details page, select a key pair to enable SSH access to the instances in your

environment. Keep the default values for everything else and click Next.

Note

If you haven't used key pairs before, see Amazon EC2 Key Pairs in the Amazon EC2 User

Guide for Linux Instances.You can also skip key pair assignment and complete this tutorial

without connecting to an instance.

13. Review the information on the final page and click Launch.

The AWS Management Console redirects you to the management dashboard for your new environment.

This screen shows the health status of the environment and events output by the Elastic Beanstalk service.

When the status is Green, click the URL next to the environment name to see your new website.

Connect to a Container Instance

So how does it all work? Next you will connect to an EC2 instance in your Elastic Beanstalk environment

to see some of the moving parts in action.

First, identify the instance and note its public IP address, which is available in the Amazon EC2 console

at https://console.aws.amazon.com/ec2/. If multiple instances are running and you have trouble identifying

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Connect to a Container Instance

the one the belongs to your environment, read through the events on the environment dashboard and

find the instance ID.This ID appears in an event listing when Elastic Beanstalk launches an EC2 instance.

Search for the instance ID in the Amazon EC2 console and view its details to find the public IP address.

Next, use an SSH client and your private key file to connect to the instance. Use the following settings:

SSH Settings

• Address – The public IP address or DNS name of the EC2 instance.

• Port – 22. This port is opened for ingress by Elastic BeanstalkBeanstalk when you select an Amazon

EC2 key pair during environment configuration.

• User Name – ec2-user.This is the default user name for EC2 instances running Amazon Linux.

• Private Key – Your private key file.

For full instructions on using SSH to connect to an EC2 instance, see Connecting to Your Linux Instance

Using SSH in the Amazon EC2 User Guide for Linux Instances.

Now that your connected to the EC2 instance hosting your docker containers, you can see how things

are set up. Run ls on /var/app/current:

[ec2-user@ip-10-0-0-117 ~]$ ls /var/app/current

Dockerrun.aws.json php-app proxy

This directory contains the files from the source bundle that you uploaded to Elastic Beanstalk during

environment creation.

[ec2-user@ip-10-0-0-117 ~]$ ls /var/log/containers

nginx nginx-proxy-ffffd873ada5-stdouterr.log rotated

nginx-66a4fd37eb63-stdouterr.log php-app

nginx-proxy php-app-b894601a1364-stdouterr.log

This is where logs are created on the container instance and collected by Elastic Beanstalk. Elastic

Beanstalk creates a volume in this directory for each container, which you mount to the container location

where logs are written.

You can also take a look at Docker to see the running containers with docker ps.

[ec2-user@ip-10-0-0-117 ~]$ sudo docker ps

CONTAINER ID IMAGE COMMAND

CREATED STATUS PORTS NAMES

ffffd873ada5 nginx:1.7 "nginx -g 'daemon of

About an hour ago Up About an hour 443/tcp, 0.0.0.0:80->80/tcp ecs-eb-

dv-example-env-ycmk5geqrm-2-nginx-proxy-90fce996cc8cbecb2800

b894601a1364 php:5-fpm "php-fpm"

About an hour ago Up About an hour 9000/tcp ecs-eb-

dv-example-env-ycmk5geqrm-2-php-app-cec0918ed1a3a49a8001

09fb19828e38 amazon/amazon-ecs-agent:latest "/agent"

About an hour ago Up About an hour 127.0.0.1:51678->51678/tcp ecs-agent

This shows the two running containers that you deployed, as well as the Amazon ECS container agent

that coordinated the deployment.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Connect to a Container Instance

Inspect the Amazon ECS Container Agent

EC2 instances in a Multicontainer Docker environment on Elastic Beanstalk run an agent process in a

Docker container.This agent connects to the Amazon ECS service in order to coordinate container

deployments.These deployments run as tasks in Amazon ECS, which are configured in task definition

files. Elastic Beanstalk creates these task definition files based on the Dockerrun.aws.json that you

upload in a source bundle.

Check the status of the container agent with an HTTP get request to

http://localhost:51678/v1/metadata:

[ec2-user@ip-10-0-0-117 ~]$ curl http://localhost:51678/v1/metadata

{

"Cluster":"eb-dv-example-env-qpoxiguye24",

"ContainerInstanceArn":"arn:aws:ecs:us-east-1:123456789012:container-in

stance/6a72af64-2838-400d-be09-3ab2d836ebcd"

}

This structure shows the name of the Amazon ECS cluster, and the ARN (Amazon Resource Name) of

the cluster instance (the EC2 instance that you are connected to).

For more information, make an HTTP get request to information is available at

http://localhost:51678/v1/tasks:

[ec2-user@ip-10-0-0-117 ~]$ curl http://localhost:51678/v1/tasks

{

"Tasks":[

{

"Arn":"arn:aws:ecs:us-east-1:123456789012:task/3ff2bf0f-790d-4f6d-affb-

5b127b3b6e4a",

"DesiredStatus":"RUNNING",

"KnownStatus":"RUNNING",

"Family":"eb-dv-example-env-qpoxiguye24",

"Version":"2",

"Containers":[

{

"Dock

erId":"b894601a1364a438156a239813c77cdef17040785bc4d5e49349470dc1556b15",

"DockerName":"ecs-eb-dv-exampl e-env-qpoxiguye24-2-php-app-

cec0918ed1a3a49a8001",

"Name":"php-app"

{

"Dock

erId":"ffffd873ada5f537c88862cce4e1de7ec3edf962645982fb236961c833a5d0fe",

"DockerName":"ecs-eb-dv-example-env-qpoxiguye24-2-nginx-proxy-

90fce996cc8cbecb2800",

"Name":"nginx-proxy"

}

]

}

]

}

This structure describes the task that is run to deploy the two docker containers from this turorial's example

project.The following information is displayed:

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Inspect the Amazon ECS Container Agent

• KnownStatus – The RUNNING status indicates that the containers are still active.

• Family – The name of the task definition that Elastic Beanstalk created from Dockerrun.aws.json.

• Version – The version of the task definition.This is incremented each time the task definition file is

updated.

• Containers – Information about the containers running on the instance.

Even more information is available from the Amazon ECS service itself, which you can call using the

AWS Command Line Interface. For instructions on using the AWS CLI with Amazon ECS, and information

about Amazon ECS in general, see the Amazon ECS User Guide.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Inspect the Amazon ECS Container Agent

Deploying Elastic Beanstalk

Applications from Preconfigured

Docker Containers

Topics

• Getting Started with Preconfigured Docker Containers (p. 87)

• Example: Using a Dockerfile to Customize and Configure a Preconfigured Docker Platform (p. 89)

Elastic Beanstalk supports Docker containers that are based on the language stacks provided in the

Docker Official Repositories.You can use preconfigured Docker containers to develop and test your

application locally and then deploy the application in an Elastic Beanstalk environment that is identical

to your local environment.

For an end-to-end walkthrough about deploying an application to Elastic Beanstalk using a preconfigured

Docker container, see Getting Started with Preconfigured Docker Containers (p. 87).

For more information about supported platforms for preconfigured Docker containers, see Docker -

Preconfigured (p. 22).

Getting Started with Preconfigured Docker

Containers

This section walks you through how to develop a sample application locally and then deploy your application

to Elastic Beanstalk with a preconfigured Docker container.

Set Up Your Local Development Environment

For this walkthrough we will use a Python Flask “Hello World” application.

To set up your develop environment

1. Create a new folder for the sample application.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Getting Started with Preconfigured Docker Containers

$ mkdir eb-flask-sample

$ cd eb-flask-sample

2. In the application's root folder, create an application.py file. In the file, include the following:

from flask import Flask

app = Flask(__name__)

@app.route('/')

def hello_world():

return 'Hello World!'

if __name__ == '__main__':

app.run()

3. In the application's root folder, create a requirements.txt file. In the file, include the following:

flask

Develop and Test Locally

To develop a sample Python Flask application

1. Add a Dockerfile to your application’s root folder. In the file, specify the AWS Elastic Beanstalk

Docker base image to be used to run your local preconfigured Docker container and against which

Elastic Beanstalk runs any subsequent Dockerfile instructions by including the following:

# For Python 3.4

FROM amazon/aws-eb-python:3.4.2-onbuild-3.5.1

AWS Elastic Beanstalk also supports Docker images for Glassfish 4.1 Java 8 and Glassfish 4.0 Java

7. For their Docker image names, see Supported Platforms (p.19). For more information about using

a Dockerfile, see Single Container Docker Configurations (p. 68).

2. Build the Docker image.

$ docker build –t my-app-image .

3. Run the Docker container from the image.

Note

You must include the -p flag to map port 8080 on the container to the localhost port 3000.

Elastic Beanstalk Docker containers always expose the application on port 8080 on the

container.The -it flag runs the image as an interactive process. The -rm flag cleans up

the container file system when the container exits.You can optionally include the -d flag to

run the image as a daemon.

$ docker run –it --rm -p 3000:8080 my-app-image

4. To view the sample application, type the following URL into your web browser.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Develop and Test Locally

http://localhost:3000

Deploy to Elastic Beanstalk

After testing your application, you are ready to deploy it to Elastic Beanstalk.

To deploy your application to Elastic Beanstalk

1. In your application's root folder, rename the Dockerfile to Dockerfile.local. This step is

required for Elastic Beanstalk to use the Dockerfile that contains the correct instructions for Elastic

Beanstalk to build a customized Docker image on each Amazon EC2 instance in your Elastic Beanstalk

environment.

2. Create an application source bundle. For more information, see Creating an Application Source

Bundle (p. 294).

3. To create a new Elastic Beanstalk application to which you can deploy your application, see Creating

New Applications (p. 279). At the appropriate step, on the Environment Type page, in the Predefined

configuration list, under Preconfigured - Docker, click Python.

Example: Using a Dockerfile to Customize and

Configure a Preconfigured Docker Platform

With preconfigured Docker platforms you cannot use a configuration file to customize and configure the

software that your application depends on. If you want to customize the preconfigured Docker platform

to install additional software packages that your application needs, you can add a Dockerfile to your

application's root folder.The following example customizes the Python 3.4 platform by adding PostgreSQL

dependencies.

If you want to use additional AWS resources (such as Amazon DynamoDB or Amazon Simple Notification

Service), modify the proxy server or modify the operating system configuration for your Elastic Beanstalk

environment. For more information about using configuration files, see Customizing and Configuring

Elastic Beanstalk Environments (p. 430).

# Use the AWS Elastic Beanstalk Python 3.4 image

FROM amazon/aws-eb-python:3.4.2-onbuild-3.5.1

# Exposes port 8080

EXPOSE 8080

# Install PostgreSQL dependencies

RUN apt-get update && \

apt-get install -y postgresql libpq-dev && \

rm -rf /var/lib/apt/lists/*

Note

Elastic Beanstalk preconfigured Docker platforms for Glassfish and Python require you to expose

port 8080. Elastic Beanstalk preconfigured Docker platforms for Go require you to expose port

3000.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Deploy to Elastic Beanstalk

Deploying Go Applications to

Elastic Beanstalk Applications

Elastic Beanstalk supports applications that are developed using the Go programming language (sometimes

called Golang). Elastic Beanstalk supports Docker containers that are based on the language stacks

provided in the Docker Official Repositories.You can use Elastic Beanstalk preconfigured Docker containers

to develop and test your Go application locally and then deploy the application in an Elastic Beanstalk

environment that is identical to your local environment.

For an end-to-end walkthrough about deploying a Go application to Elastic Beanstalk using a preconfigured

Docker container, see Getting Started with Go Preconfigured Docker Containers (p. 90).

For more information about supported platforms for preconfigured Docker containers, including the

containers for Go applications, see Docker - Preconfigured (p. 22).

Getting Started with Go Preconfigured Docker

Containers

Follow the steps here to walk you through the process of deploying a Go application to Elastic Beanstalk

with a preconfigured Docker container for Go.

Set Up Your Local Development Environment

This tutorial uses a Go “Hello World” application.

To set up your develop environment

1. Create a new folder for the sample application.

$ mkdir eb-go-sample

$ cd eb-go-sample

2. In the application's root folder, create a file with the name server.go. In the file, include the following:

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Getting Started with Go Preconfigured Docker

Containers

package main

import "github.com/go-martini/martini"

func main() {

m := martini.Classic()

m.Get("/", func() string {

return "Hello world!"

})

m.Run()

}

Note

• The application source bundle must include a package called main.Within that package,

you must have a main function for the container to execute.

• Dependencies that need to be imported (for example, the Martini package, go-martini)

will be downloaded to the container and installed during deployment. Therefore, you do

not need to include the dependencies in the application source bundle that you upload

to Elastic Beanstalk.

• Elastic Beanstalk sets the container’s GOPATH environment variable to /go.

Develop and Test Locally Using Docker

With your environment set up, you're ready to create and test your Go application.

To develop a sample Go application

1. Add a Dockerfile to your application’s root folder. In the file, specify the Elastic Beanstalk Docker

base image to use to run your local preconfigured Docker container. Elastic Beanstalk uses this

image to run any subsequent Dockerfile instructions.

Note

Include only the instruction with the Docker image name for your platform version. For

preconfigured Docker image names, see Supported Platforms (p.19). For more information

about using a Dockerfile, see Single Container Docker Configurations (p. 68). For an

example Dockerfile for preconfigured Docker platforms, see Example: Using a Dockerfile

to Customize and Configure a Preconfigured Docker Platform (p. 89).

You can use the following example:

# For Go 1.3

FROM golang:1.3.3-onbuild

# For Go 1.4

FROM golang:1.4.1-onbuild

2. Build the Docker image.

$ docker build –t my-app-image .

3. Run the Docker container from the image.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Develop and Test Locally Using Docker

Note

You must include the -p flag to map port 3000 on the container to the localhost port 8080.

Elastic Beanstalk preconfigured Docker containers for Go applications always expose the

application on port 3000 on the container.The -it flag runs the image as an interactive

process.The -rm flag cleans up the container file system when the container exits.You

can optionally include the -d flag to run the image as a daemon.

$ docker run –it --rm -p 8080:3000 my-app-image

4. To view the sample application, type the following URL into your web browser.

http://localhost:8080

Deploy to Elastic Beanstalk

After testing your application, you are ready to deploy it to Elastic Beanstalk.

To deploy your application to Elastic Beanstalk

1. In your application's root folder, rename the Dockerfile to Dockerfile.local. This step is

required for Elastic Beanstalk to use the Dockerfile that contains the correct instructions for Elastic

Beanstalk to build a customized Docker image on each Amazon EC2 instance in your Elastic Beanstalk

environment.

Note

You do not need to perform this step if your Dockerfile includes instructions that modify

the base Go Docker image.You do not need to use a Dockerfile if your Dockerfile

includes only a FROM line to specify the base image from which to build the container. In

that situation, the Dockerfile is redundant.

2. Create an application source bundle. For more information, see Creating an Application Source

Bundle (p. 294).

3. Create an Elastic Beanstalk application to which you can deploy your application. For step-by-step

instructions, see Creating New Applications (p. 279). At the appropriate step, on the Environment

Type page, in the Predefined configuration list, under Preconfigured - Docker, click Go.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Deploy to Elastic Beanstalk

Creating and Deploying Elastic

Beanstalk Applications in Java

Using AWS Toolkit for Eclipse

Topics

• Develop, Test, and Deploy (p. 93)

• Importing Existing Environments into Eclipse (p. 102)

• Using Custom Environment Properties with Elastic Beanstalk (p. 102)

• Using Amazon RDS and MySQL Connector/J (p. 105)

• Managing Multiple AWS Accounts (p. 110)

• Viewing Events (p. 111)

• Managing Elastic Beanstalk Application Environments (p. 112)

• Listing and Connecting to Server Instances (p. 123)

• Terminating an Environment (p. 123)

• Tools (p. 124)

• Resources (p. 124)

The first part of this topic provides step-by-step instructions for creating, testing, deploying, and redeploying

your Java application to Elastic Beanstalk using the AWS Toolkit for Eclipse.The second part of this topic

provides information on how you can manage and configure your applications and environments using

the AWS Toolkit for Eclipse. For more information about prerequisites and installing the AWS Toolkit for

Eclipse, go to http://aws.amazon.com/eclipse.You can also check out the Using AWS Elastic Beanstalk

with the AWS Toolkit for Eclipse video.This topic also provides useful information covering tools, how-to

topics, and additional resources for Java developers.

Develop,Test, and Deploy

Topics

• Create Project (p. 94)

• Test Locally (p. 96)

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Develop,Test, and Deploy

• Deploy to AWS Elastic Beanstalk (p. 98)

• Debug/View Logs (p. 101)

• Edit the Application and Redeploy (p. 101)

• Deploy to Production (p. 102)

The following diagram illustrates a typical software development life cycle that includes deploying your

application to Elastic Beanstalk.

After developing and testing your application locally, you typically deploy your application to AWS Elastic

Beanstalk. After deployment, your application will be live at a URL such as

http://myexampleapp-wpams3yrvj.elasticbeanstalk.com.

If you want to replace the URL with a custom domain name, you can use Amazon Route 53, a highly

available and scalable Domain Name System (DNS) web service.You can point your domain name to

the Amazon Route 53 CNAME <yourappname>.elasticbeanstalk.com. Contact your DNS provider to set

this up. For information about how to map your root domain to your Elastic Load Balancer, see Using

Elastic Beanstalk with Amazon Route 53 to Map Your Domain to Your Load Balancer (p. 528).

Because your application is live, you should consider setting up multiple environments, such as a testing

environment and a production environment.You can use the AWS Toolkit for Eclipse to set up different

AWS accounts for testing, staging, and production. For information about managing multiple accounts,

see Managing Multiple AWS Accounts (p. 110).

After you remotely test and debug your Elastic Beanstalk application, you can make any updates and

then redeploy it to Elastic Beanstalk. After you are satisfied with all of your changes, you can upload the

latest version to your production environment.The following sections explain each stage of the software

development life cycle.

Create Project

The AWS Toolkit provides an AWS Java web project template for use in Eclipse.The template creates

a web tools platform (WTP) dynamic web project that includes the AWS SDK for Java in the project's

classpath.Your AWS account credentials and a simple index.jsp file are provided to help you get

started.The following instructions assume you have installed both the Eclipse IDE for Java EE Developers

and the AWS Toolkit plug-in. For more information, see Setting Up the AWS Toolkit for Eclipse.

Note

For information about what versions of Java are supported, see Supported Platforms (p. 19).

To create a new AWS Java web project in Eclipse

1. In Eclipse, make sure the toolbar and the AWS icon are visible.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Create Project

2. On the toolbar, click the arrow next to the AWS icon and choose New AWS Java Web Project.

3. In the New AWS Java Web Project wizard, click Project name, and then enter the name of your

AWS Java Web Project.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Create Project

4. Select the AWS account you want to use to deploy your application. If you haven't already configured

an account, click Configure AWS accounts to add a new account. For instructions on how to add

a new account, go to Managing Multiple AWS Accounts (p. 110).

5. Select the application you want to start from.

6. Click Finish.

A new AWS Java web project is created inside your Eclipse workspace.To help you get started developing

your project, a basic index.jsp file is included inside your WebContent folder.Your AWS security

credentials are included in the AwsCredentials.properties file inside your src folder.

Test Locally

You can test and debug your application before you deploy it to Elastic Beanstalk using the built-in WTP

tools.

To test and debug your application locally

1. If Eclipse isn't displaying Project Explorer view, do one of the following:

• In the Java EE perspective, click the Window menu, click Show View, and then click Project

Explorer.

• In the AWS Management perspective, click the Window menu, click Show View, expand General,

and then click Project Explorer.

2. In the Project Explorer tab, right-click your Java web project, choose Run As, Run On Server.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Test Locally

Note

If the Run on Server option does not appear, ensure that you have the Web Tools Platform

Eclipse extensions installed.The WTP is included with Eclipse if you install the Eclipse IDE

for Java EE Developers.The tools must be installed when your project is created for the

option to appear.

3. In the Run On Server wizard, click Manually define a new server.

4. Under Select the server type, expand Apache, and then click Tomcat v6.0 Server or Tomcat v7.0

Server.

5. Click Next.

6. You might be prompted to install Apache. If you are using Microsoft Windows, you can click Download

and Install to install the software. After you install the software, click Finish.

Note

You might need to manually create a Tomcat server.This includes going directly to

http://apache.org to download Apache Tomcat, extracting the compressed file containing

Apache Tomcat onto your computer, and then adding the Apache Tomcat runtimes. For

more information, go to the "Creating an Apache Tomcat Server" topic of the Eclipse online

documentation at help.eclipse.org.

After you create a Tomcat server and add the Apache Tomcat runtimes, go to Step 2 in

these procedures.

Your application should be visible on the localhost.

Note

Environment properties that are typically provided by Elastic Beanstalk, such as RDS_HOSTNAME

(when using RDS), are not available to applications running locally.

After you test your application, you can deploy to Elastic Beanstalk.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Test Locally

Deploy to AWS Elastic Beanstalk

The Elastic Beanstalk server is an Eclipse WTP server with added functionality for restarting, publishing,

and terminating your Java web application.The Elastic Beanstalk server in Eclipse represents an Elastic

Beanstalk environment. An environment is a running instance of an application on the AWS platform.

Define Your Server

Before deploying your application, you must define your server and configure your application.

To define your Java web application server

1. In Eclipse, right-click your Java web project in the Project Explorer view. Choose Amazon Web

Services, Deploy to AWS Elastic Beanstalk.

2. In the Run On Server wizard, select Manually define a new server.

3. Under Select the server type, expand Amazon Web Services, and then click Elastic Beanstalk

for Tomcat 6 or Elastic Beanstalk for Tomcat 7.

4. If necessary, enter the server's host name and server name in the provided fields. Click Next.

You have defined your AWS Java web application server.You must use the Configure Application and

Environment options to configure your AWS Java web application before deployment.

Configure

Each application has a configuration and a version. A specific application instance is called an environment.

An environment can have only one version at a time, but you can have multiple simultaneous environments

running the same or different versions. AWS resources created for an environment can include one Elastic

Load Balancing load balancer, an Auto Scaling group, and one or more Amazon EC2 instances.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Deploy to AWS Elastic Beanstalk

To configure your Amazon web application

1. In the Configure Application and Environment view of the Run On Server wizard, click Region,

and then select your Amazon Web Services region.

2. Enter an application name and, if desired, provide an application description.

3. Enter an environment name and, if desired, provide an environment description.The environment

name must be unique within your AWS account.

4. Select the Type of environment that you want.

You can select either Load Balanced or a Single Instance environment. For more information, see

Environment Types (p. 345).

Note

For single-instance environments, load balancing, autoscaling, and the health check URL

settings don't apply.

5. Click Next.

6. Click Deploy with a key pair.

API Version 2010-12-01

Elastic Beanstalk Developer Guide

Deploy to AWS Elastic Beanstalk

7. Right-click anywhere inside the key pair list menu and select New Key Pair.

8. For Key Pair Name, enter a key pair name. For Private Key Directory, enter a private key directory

or click Browse and select a directory. Click OK and select the newly created key pair in the key

pair list menu.

9. Select Use incremental deployment to deploy only the changed files. An incremental deployment

is faster because you are updating only the files that changed instead of all the files.

10. Select an instance profile.

If you are using a nonlegacy container, you have the option to select an instance profile. If you are

using a legacy container, this option does not appear in the dialog box. An instance profile provides

applications and services access to AWS resources using temporary security credentials. For example,

if your application requires access to Amazon DynamoDB, it must use AWS security credentials to

make an API request.The application can use the temporary security credentials so you do not have

to store long-term credentials on an EC2 instance or update the EC2 instance every time the

credentials are rotated. In addition, Elastic Beanstalk requires an instance profile to rotate logs to

Amazon S3.The Instance Profile list displays the profiles available for your Elastic Beanstalk

environment. If you do not have an instance profile, you can select Create a default instance profile.

Elastic Beanstalk creates a default instance profile and updates the Amazon S3 bucket policy to

allow log rotation. If you choose to not use the default instance profile, you need to grant permissions

for Elastic Beanstalk to rotate logs. For instructions, see Using a Custom Instance Profile (p. 577).

For more information about log rotation, see Elastic Beanstalk Environment Configurations (p. 389).

For more information about using instance profiles with Elastic Beanstalk, see Using IAM Roles with

Elastic Beanstalk (p. 568).

Note

Users must have permission to create a default profile. For more information, see Granting

IAM Users Permissions to Create and Pass IAM Roles (p. 568).

11. Click Finish.

After you finish the wizard, you are prompted to enter a new version label for your application version,

and a new server appears in the Server view.Your Java web project will be exported as a .war file,

uploaded to Amazon S3, and registered as a new application version with Elastic Beanstalk.The Elastic

API Version 2010-12-01

100

Elastic Beanstalk Developer Guide

Deploy to AWS Elastic Beanstalk

Beanstalk deployment feature monitors your environment until it becomes available with the newly

deployed code and opens your application in a web browser when it's ready.

Debug/View Logs

To investigate any issues, you can view logs. For information about viewing logs, see Working with

Logs (p. 415). If you need to test remotely, you can connect to your EC2 instances. For instructions on

how to connect to your instance, see Listing and Connecting to Server Instances (p. 413).

Edit the Application and Redeploy

Now that you have tested your application, it is easy to edit and redeploy it and to see the results in

moments.Typically, when you redeploy your application, all of the files get updated. However, if you

choose to do an incremental deployment, the toolkit updates the modified files, making your deployment

faster.

To choose to use incremental deployments

1. If Eclipse isn't displaying AWS Explorer view, in the menu choose Window, Show View, AWS

Explorer. In the AWS Explorer pane, expand the Elastic Beanstalk node and your application

node.

2. Double-click your Elastic Beanstalk environment.

3. In the Overview tab, expand the AWS Elastic Beanstalk Deployment tab, and then select Use

Incremental Deployments.

To edit and redeploy your Java web application

1. In Eclipse, locate and double-click the index.jsp file in the Project Explorer or Package Explorer

view. Edit the source contained in the file.

2. Right-click your Java web project in the Project Explorer or Package Explorer view and choose

Amazon Web Services, Deploy to AWS Elastic Beanstalk.

3. In the Run On Server wizard, select Choose an existing server, and click Finish.

Note

If you launched a new environment using the AWS Management Console, you will need to

import your existing environments into Eclipse. For more information, see Importing Existing

Environments into Eclipse (p. 102).

When the application has been deployed successfully, index.jsp is displayed in Eclipse and shows

any edits you made.

API Version 2010-12-01

101

Elastic Beanstalk Developer Guide

Debug/View Logs

Deploy to Production

When you are satisfied with all of the changes that you want to make to your application, you can deploy

your application to your production environment.To deploy the existing version of the application to

production with zero downtime, follow the steps at Deploying Versions with Zero Downtime (p. 318).You

can also create a new environment inside Eclipse, but you will need to specify a new version for your

application. For instructions on deploying to Elastic Beanstalk inside Eclipse, see Deploy to AWS Elastic

Beanstalk (p. 98).

Importing Existing Environments into Eclipse

You can import existing environments that you created in the AWS Management Console into Eclipse.

To import existing environments, expand the AWS Elastic Beanstalk node and double-click on an

environment in the AWS Explorer inside Eclipse.You can now deploy your Elastic Beanstalk applications

to this environment.

Using Custom Environment Properties with

Elastic Beanstalk

You can use the AWS Management Console or the AWS Toolkit for Eclipse to set environment properties

that Elastic Beanstalk passes to your server instances. Environment properties are specific to your

application environment and are not actual (shell) environment variables. More specifically, PARAM1,

PARAM2, etc. are system properties passed into the JVM at startup using the -D flag.You can use them

to pass database connection strings, security credentials, or other information that you don't want to

hard-code into your application. Storing this information in environment properties can help increase the

portability and scalability of your application.You do not need to recompile your source code when you

move between environments.You can acquire them with System.getProperty(name).

Setting Custom Environment Properties with AWS

Toolkit for Eclipse

The following example sets the JDBC_CONNECTION_STRING and PARAM1 environment properties in the

AWS Toolkit for Eclipse. After you set these properties, they become available to your Elastic Beanstalk

application as system properties called JDBC_CONNECTION_STRING and PARAM1, respectively.

The procedure for setting other environment properties is the same.You can use PARAM1 through PARAM5

for any purpose you choose, but you cannot rename the properties.

Note

The AWS Toolkit for Eclipse does not yet support modifying environment configuration, including

environment variables, for environments in a VPC. Unless you have an older account using EC2

Classic, you must use the AWS Management Console (described in the next section) or the EB

CLI (version 3 or newer) (p. 620)

To set environment properties for your Elastic Beanstalk application

1. If Eclipse isn't displaying the AWS Explorer view, choose Window, Show View, Other. Expand

AWS Toolkit and then click AWS Explorer.

2. In the AWS Explorer pane, expand Elastic Beanstalk, expand the node for your application, and

then double-click your Elastic Beanstalk environment.

API Version 2010-12-01

102

Elastic Beanstalk Developer Guide

Deploy to Production

3. At the bottom of the pane for your environment, click the Advanced tab.

4. Under aws:elasticbeanstalk:application:environment, click JDBC_CONNECTION_STRING and

then type a connection string. For example, the following JDBC connection string would connect to

a MySQL database instance on port 3306 of localhost, with a user name of me and a password of

mypassword:

jdbc:mysql://localhost:3306/mydatabase?user=me&password=mypassword

This will be accessible to your Elastic Beanstalk application as a system property called

JDBC_CONNECTION_STRING.

5. Click PARAM1 and then type a string. For example:

My test parameter.

This will be accessible to your Elastic Beanstalk application as a system property called PARAM1.

6. Press Ctrl+S on the keyboard or choose File, Save to save your changes to the environment

configuration. Changes are reflected in about one minute.

Setting Custom Environment Properties with AWS

Management Console

The following example sets the JDBC_CONNECTION_STRING and PARAM1 environment properties in the

AWS Management Console. After you set these properties, they become available to your Elastic Beanstalk

application as system properties called JDBC_CONNECTION_STRING and PARAM1, respectively.

The procedure for setting other environment properties is the same.You can use PARAM1 through PARAM5

for any purpose you choose, but you cannot rename the properties.

To set environment properties for your Elastic Beanstalk application

1. Open the Elastic Beanstalk console at https://console.aws.amazon.com/elasticbeanstalk/.

2. From the Elastic Beanstalk console applications page, click the environment name to view its

dashboard.

API Version 2010-12-01

103

Elastic Beanstalk Developer Guide

Setting Custom Environment Properties with AWS

Management Console

3. In the navigation pane, click Configuration.

On the Configuration page, in the Software Configuration section, click .

5. Under Environment Properties, next to JDBC_CONNECTION_STRING, in the Property Value

column, type a connection string.

For example, the following JDBC connection string would connect to a MySQL database instance

on port 3306 of localhost, with a username of me and a password of mypassword:

jdbc:mysql://localhost:3306/mydatabase?user=me&password=mypassword

This will be accessible to your Elastic Beanstalk application as a system property called

JDBC_CONNECTION_STRING.

6. Next to PARAM1, in the Property Value column, type a string, for example: My test parameter.

This parameter will be accessible to your Elastic Beanstalk application as a system property called

PARAM1.

7. Click Save.

Elastic Beanstalk updates your environment.This takes about one minute.

Accessing Custom Environment Properties

After you set your environment properties for your Elastic Beanstalk application, you can access the

environment properties from your code. For example, the following code snippet shows how to access

the Elastic Beanstalk environment properties using JavaScript in a JavaServer Page (JSP):

<p>

The JDBC_CONNECTION_STRING environment property is:

<%= System.getProperty("JDBC_CONNECTION_STRING") %>

</p>

<p>

The PARAM1 environment property is:

<%= System.getProperty("PARAM1") %>

</p>

API Version 2010-12-01

104

Elastic Beanstalk Developer Guide

Accessing Custom Environment Properties

Using Amazon RDS and MySQL Connector/J

With Amazon Relational Database Service, you can quickly and easily provision and maintain a MySQL,

Oracle, or Microsoft SQL Server instance in the cloud. For more information about Amazon RDS, go to

http://aws.amazon.com/rds/.

This topic explains how you can use Amazon RDS and MySQL Connector/J with your Elastic Beanstalk

Java application.

Note

The instructions in this topic are for nonlegacy container types. If you have deployed an Elastic

Beanstalk application using a legacy container type, we recommend that you migrate to a

nonlegacy container type to gain access to new features. For instructions on how to check the

container type and migrate your application, see Migrating Your Application from a Legacy

Container Type (p. 426). For instructions on using MySQL Connector/J with applications running

on legacy container types, see Using Amazon RDS and MySQL Connector/J (Legacy Container

Types) (p. 816).

To use Amazon RDS from your Elastic Beanstalk application, you need to do the following:

1. Create an Amazon RDS DB instance.

2. Download and install MySQL Connector/J.

3. Establish a database connection in your code by using the connectivity information for your Amazon

RDS DB instance.

4. Deploy your application to Elastic Beanstalk.

This topic walks you through the following:

• Using a new Amazon RDS DB instance with your application

• Using an existing Amazon RDS DB instance with your application

Using a New Amazon RDS DB Instance with Java

This topic walks you through creating a new Amazon RDS DB Instance and using it with your Java

application.

1. Sign in to the AWS Management Console and open the Elastic Beanstalk console at https://

console.aws.amazon.com/elasticbeanstalk/.

2. Click your environment name and select Configuration.

3. Scroll down to the Data Tier section and click Create a new RDS database.

4. Enter a user name and password and click Save. Click Save again on the message about instance

profiles, if shown. Elastic Beanstalk updates your environment to include the new RDS instance and

provides connection information to the web container as environment properties.

5. Download and install MySQL Connector/J for your development environment. For download and

installation instructions, go to http://dev.mysql.com/downloads/connector/j.

6. Copy the MySQL Connector/J .jar file into the project's WebContent/WEB-INF/lib directory.

7. Right click on WebContent/WEB-INF/lib/mysql_connector_java_5.1.34_bin.jar and click

Add to Build Path to add the library to the classpath.

8. Test the database connection by adding the following code to the main view of your Java Web

Application (index.jsp).

API Version 2010-12-01

105

Elastic Beanstalk Developer Guide

Using Amazon RDS and MySQL Connector/J

<%@ page import="java.sql.*" %>

// Read RDS Connection Information from the Environment

String dbName = System.getProperty("RDS_DB_NAME");

String userName = System.getProperty("RDS_USERNAME");

String password = System.getProperty("RDS_PASSWORD");

String hostname = System.getProperty("RDS_HOSTNAME");

String port = System.getProperty("RDS_PORT");

String jdbcUrl = "jdbc:mysql://" + hostname + ":" +

port + "/" + dbName + "?user=" + userName + "&password=" + password;

// Load the JDBC Driver

try {

System.out.println("Loading driver...");

Class.forName("com.mysql.jdbc.Driver");

System.out.println("Driver loaded!");

} catch (ClassNotFoundException e) {

throw new RuntimeException("Cannot find the driver in the classpath!",

e);

}

Connection conn = null;

Statement setupStatement = null;

Statement readStatement = null;

ResultSet resultSet = null;

String results = "";

int numresults = 0;

String statement = null;

try {

// Create connection to RDS instance

conn = DriverManager.getConnection(jdbcUrl);

// Create a table and write two rows

setupStatement = conn.createStatement();

String createTable = "CREATE TABLE Beanstalk (Resource char(50));";

String insertRow1 = "INSERT INTO Beanstalk (Resource) VALUES ('EC2 In

stance');";

String insertRow2 = "INSERT INTO Beanstalk (Resource) VALUES ('RDS In

stance');";

setupStatement.addBatch(createTable);

setupStatement.addBatch(insertRow1);

setupStatement.addBatch(insertRow2);

setupStatement.executeBatch();

setupStatement.close();

} catch (SQLException ex) {

// handle any errors

System.out.println("SQLException: " + ex.getMessage());

System.out.println("SQLState: " + ex.getSQLState());

System.out.println("VendorError: " + ex.getErrorCode());

} finally {

System.out.println("Closing the connection.");

if (conn != null) try { conn.close(); } catch (SQLException ignore) {}

}

try {

API Version 2010-12-01

106

Elastic Beanstalk Developer Guide

Using a New Amazon RDS DB Instance with Java

conn = DriverManager.getConnection(jdbcUrl);

readStatement = conn.createStatement();

resultSet = readStatement.executeQuery("SELECT Resource FROM Beanstalk;");

resultSet.first();

results = resultSet.getString("Resource");

resultSet.next();

results += ", " + resultSet.getString("Resource");

resultSet.close();

readStatement.close();

conn.close();

} catch (SQLException ex) {

// handle any errors

System.out.println("SQLException: " + ex.getMessage());

System.out.println("SQLState: " + ex.getSQLState());

System.out.println("VendorError: " + ex.getErrorCode());

} finally {

System.out.println("Closing the connection.");

if (conn != null) try { conn.close(); } catch (SQLException ignore)

{}

}

9. Place the following code in the body of the html portion of index.jsp to display the results.

<p>Established connection to RDS. Read first two rows: <%= results %></p>

10. Right-click your project in the Package Explorer and choose Run As, Run on Server.

11. If your project is not configured to always deploy to the same environment, select the environment

that your application is currently running on and click Finish.

For more information on getting started using the MySQL Connector/J to access your MySQL database,

go to http://dev.mysql.com/doc/connector-j/en/index.html.

Using an Existing Amazon RDS DB Instance with

Java

With Amazon Relational Database Service you can quickly and easily provision and maintain a MySQL

Server instance in the cloud. This topic discusses how you can use Amazon RDS and the MySQL

Connector/J with your Elastic Beanstalk application.

To use an existing Amazon RDS DB Instance and Java from your Elastic Beanstalk

application

1. Create an Elastic Beanstalk environment in one of the following ways:

• Create a new application with a new environment. For instructions using the Elastic Beanstalk

console, see Creating New Applications (p. 279). For instructions using Eclipse, see Develop, Test,

and Deploy (p. 93).You do not need to create an Amazon RDS DB Instance with this environment

because you already have an existing Amazon RDS DB Instance.

API Version 2010-12-01

107

Elastic Beanstalk Developer Guide

Using an Existing Amazon RDS DB Instance with Java

• Launch a new environment with an existing application version. For instructions using the Elastic

Beanstalk console, see Launching New Environments (p. 299).You do not need to create an

Amazon RDS DB instance with this environment because you already have an existing Amazon

RDS DB instance.

2. Configure your Amazon RDS DB security group to allow access from the Amazon EC2 security group

used by your Elastic Beanstalk application. For instructions on how to find the name of your EC2

security group using the AWS Management Console, see Amazon EC2 Security Groups (p.354). For

more information, go to the "Authorizing Network Access to an Amazon EC2 Security Group" section

of Working with DB Security Groups in the Amazon Relational Database Service User Guide.

3. Download and install MySQL Connector/J for your development environment. For download and

installation instructions, go to http://dev.mysql.com/downloads/connector/j.

4. Create a JDBC connection string that includesyour Amazon RDS DB instance's public DNS name,

port number, and (optionally) database name and login credentials. The following example shows a

JDBC connection string that would connect to the employees database on an Amazon RDS instance

at mydbinstance.abcdefghijkl.us-west-2.rds.amazonaws.com using port 3306, with the user name

"sa" and the password "mypassword".

jdbc:mysql://mydbinstance.abcdefghijkl.us-west-2.rds.amazonaws.com:3306/em

ployees?user=sa&password=mypassword

5. Configure your Elastic Beanstalk environment to pass the string to your Elastic Beanstalk application

as an environment property. For instructions on how to do this, go to Using Custom Environment

Properties with Elastic Beanstalk (p. 102).

6. Retrieve the JDBC connection string from the environment property passed to your server instance

from Elastic Beanstalk and use MySQL Connector/J to access your Amazon RDS database.The

following code example shows how to retrieve the JDBC_CONNECTION_STRING custom environment

property from a Java Server Page (JSP).

<p>

The JDBC_CONNECTION_STRING environment variable is:

<%= System.getProperty("JDBC_CONNECTION_STRING") %>

</p>

For more information on getting started using the MySQL Connector/J to access your MySQL

database, go to http://dev.mysql.com/doc/connector-j/en/index.html.

7. Copy the MySQL Connector/J .jar file into the Tomcat WEB-INF/lib directory.

8. Deploy your updated application to your existing Elastic Beanstalk environment. For information on

how to deploy a new application version to an existing environment using the Elastic Beanstalk

console, see Step 4: Deploy New Version (p. 7). For information on how to deploy your application

using Eclipse, see Develop, Test, and Deploy (p. 93).

Note

To connect to Tomcat RDS environments, you must load the driver explicitly using

Class.forName(<driverClassName>) prior to the call to

DriverManager.getConnection() in the Java code.

Troubleshooting Database Connections

If and when you run into issues connecting to a database from within your application, the web container

log and database itself are two good places to look for information.

API Version 2010-12-01

108

Elastic Beanstalk Developer Guide

Troubleshooting Database Connections

Logs

You can view all of the logs from your Elastic Beanstalk environment from within Eclipse. If you don't

have the AWS Explorer view open, click the arrow next to the orange AWS icon in the toolbar and choose

Show AWS Explorer View. Expand AWS Elastic Beanstalk and your environment name, and then

right-click the server and choose Open in WTP Server Editor.

Click the log tab of the server view to see the aggregate logs from your environment. Use the refresh

button at the upper right corner of the view whenever you need to open the latest logs.

Scroll down and locate the TomCat logs from /var/log/tomcat7/catalina.out. If you loaded the

web page from our earlier example several times, you might see the following in the output.

-------------------------------------

/var/log/tomcat7/catalina.out

-------------------------------------

INFO: Server startup in 9285 ms

Loading driver...

Driver loaded!

SQLException: Table 'Beanstalk' already exists

SQLState: 42S01

VendorError: 1050

Closing the connection.

Everything sent to standard output by the web application will show up in the web container log.This

example tries to create the table on every page load and ends up catching a SQL exception on every

page load after the first one.

Note

This is okay for an example, but in real world applications you'll keep your database definitions

in schema objects, perform transactions from within model classes, and coordinate requests

with controller servlets.

RDS

You can connect directly to the Amazon RDS instance in your Elastic Beanstalk environment using the

My SQL client application.

First you'll need to open the security group to your Amazon RDS instance to allow traffic from your

computer.

1. Open the Elastic Beanstalk console at https://console.aws.amazon.com/elasticbeanstalk/.

2. Click the name of your environment and click Configuration.

Under Network Tier, in the RDS section, click the gear icon.

4. Select View in RDS Console next to the DB endpoint.

5. On the RDS Dashboard instance details page, under Security and Network, click the security group

starting with rds- next to Security Groups.

6. In the security group details, select the Inbound tab and click Edit

7. Add a rule for My SQL (similar to the one that is already there) that allows traffic from your IP address

or range.

8. Click Save. The changes take effect immediately.

Return to the Elastic Beanstalk configuration details for your environment and note the endpoint.You will

use the domain name to connect to the RDS instance.

API Version 2010-12-01

109

Elastic Beanstalk Developer Guide

Troubleshooting Database Connections

Install My SQL client and initiate a connection to the database on port 3306. In Windows, install the My

SQL Workbench application from the My SQL home page and follow the prompts.

In Linux, install the My SQL client using the package manager for your distribution.The following example

works on Ubuntu and other Debian derivatives.

// Install My SQL client

$ sudo apt-get install mysql-client-5.5

...

// Connect to database

$ mysql -h aas839jo2vwhwb.cnubrrfwfka8.us-west-2.rds.amazonaws.com -u username

-ppassword ebdb

Reading table information for completion of table and column names

You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor. Commands end with ; or \g.

Your MySQL connection id is 117

Server version: 5.5.40-log Source distribution

...

Once connected, you can run SQL commands to see the status of the database, whether your tables

and rows have been created, and other information.

mysql> SELECT Resource from Beanstalk;

+--------------+

| Resource |

+--------------+

| EC2 Instance |

| RDS Instance |

+--------------+

2 rows in set (0.01 sec)

Managing Multiple AWS Accounts

You might want to set up different AWS accounts to perform different tasks, such as testing, staging, and

production.You can use the AWS Toolkit for Eclipse to add, edit, and delete accounts easily.

To add an AWS account with the AWS Toolkit for Eclipse

1. In Eclipse, make sure the toolbar is visible. On the toolbar, click the arrow next to the AWS icon and

select Preferences.

2. Click Add account.

API Version 2010-12-01

110

Elastic Beanstalk Developer Guide

Managing Multiple AWS Accounts

3. In the Account Name text box, type the display name for the account.

4. In the Access Key ID text box, type your AWS access key ID.

5. In the Secret Access Key text box, type your AWS secret key.

For API access, you need an access key ID and secret access key. Use IAM user access keys

instead of AWS root account access keys. IAM lets you securely control access to AWS services

and resources in your AWS account. For more information about creating access keys, see How Do

I Get Security Credentials? in the AWS General Reference.

6. Click OK.

To use a different account to deploy an application to Elastic Beanstalk

1. In the Eclipse toolbar, click the arrow next to the AWS icon and select Preferences.

2. For Default Account, select the account you want to use to deploy applications to Elastic Beanstalk.

3. Click OK.

4. In the Project Explorer pane, right-click the application you want to deploy, and then select Amazon

Web Services > Deploy to Elastic Beanstalk.

Viewing Events

You can use the AWS Toolkit for Eclipse to access events and notifications associated with your application.

For more details on the most common events, see Understanding Environment Launch Events (p. 512).

To view application events

1. If Eclipse isn't displaying the AWS Explorer view, in the menu click Window > Show View > AWS

Explorer. Expand the Elastic Beanstalk node and your application node.

2. In the AWS Explorer, double-click your Elastic Beanstalk environment.

3. At the bottom of the pane, click the Events tab.

A list of the events for all environments for your application is displayed.

API Version 2010-12-01

111

Elastic Beanstalk Developer Guide

Viewing Events

Managing Elastic Beanstalk Application

Environments

Topics

• Changing Environment Configuration Settings (p. 112)

• Changing Environment Type (p. 113)

• Configuring EC2 Server Instances Using AWS Toolkit for Eclipse (p. 113)

• Configuring Elastic Load Balancing Using AWS Toolkit for Eclipse (p. 116)

• Configuring Auto Scaling Using AWS Toolkit for Eclipse (p. 118)

• Configuring Notifications Using AWS Toolkit for Eclipse (p. 120)

• Configuring Java Containers Using AWS Toolkit for Eclipse (p. 121)

With the AWS Toolkit for Eclipse and the AWS Management Console, you can change the provisioning

and configuration of the AWS resources that are used by your application environments. For information

on how to manage your application environments using the AWS Management Console, see Managing

Environments (p. 335).This section discusses the specific service settings you can edit in the AWS Toolkit

for Eclipse as part of your application environment configuration. For more about AWS Toolkit for Eclipse,

see AWS Toolkit for Eclipse Getting Started Guide.

Changing Environment Configuration Settings

When you deploy your application, Elastic Beanstalk configures a number of AWS cloud computing

services.You can control how these individual services are configured using the AWS Toolkit for Eclipse.

To edit an application's environment settings

1. If Eclipse isn't displaying the AWS Explorer view, in the menu click Window > Show View > AWS

Explorer. Expand the Elastic Beanstalk node and your application node.

2. In AWS Explorer, double-click your Elastic Beanstalk environment.

3. At the bottom of the pane, click the Configuration tab.

API Version 2010-12-01

112

Elastic Beanstalk Developer Guide

Managing Environments

You can now configure settings for the following:

• EC2 server instances

• Load balancer

• Autoscaling

• Notifications

• Environment types

• Environment properties

Changing Environment Type

In AWS Toolkit for Eclipse, the Environment Type section of your environment's Configuration tab lets

you select either Load balanced, auto scaled or a Single instance environment, depending on the

requirements of the application that you deploy. For an application that requires scalability, select Load

balanced, auto scaled. For a simple, low traffic application, select Single instance. For more information,

see Environment Types (p. 345).

Configuring EC2 Server Instances Using AWS

Toolkit for Eclipse

Amazon Elastic Compute Cloud (EC2) is a web service for launching and managing server instances in

Amazon's data centers.You can use Amazon EC2 server instances at any time, for as long as you need,

and for any legal purpose. Instances are available in different sizes and configurations. For more

information, go to the Amazon EC2 product page.

API Version 2010-12-01

113

Elastic Beanstalk Developer Guide

Environment Types

Under Server, on your environment's Configuration tab inside the Toolkit for Eclipse, you can edit the

Elastic Beanstalk environment's Amazon EC2 instance configuration.

Amazon EC2 Instance Types

Instance type displays the instance types available to your Elastic Beanstalk application. Change the

instance type to select a server with the characteristics (including memory size and CPU power) that are

most appropriate to your application. For example, applications with intensive and long-running operations

may require more CPU or memory. Elastic Beanstalk regularly checks your running instances to ensure

they are healthy. If your application consumes 95 percent or greater of the CPU, Elastic Beanstalk will

trigger an event. For more information about this event, see CPU Utilization Exceeds 95.00% (p. 513).

Note

You cannot change between 32-bit and 64-bit instance types. For example, if your application

is built on a 32-bit platform, only 32-bit instance types appear in the list.

For more information about the Amazon EC2 instance types available for your Elastic Beanstalk application,

see Instance Types in the Amazon Elastic Compute Cloud User Guide.

Amazon EC2 Security Groups

You can control access to your Elastic Beanstalk application using an Amazon EC2 Security Group. A

security group defines firewall rules for your instances.These rules specify which ingress (i.e., incoming)

network traffic should be delivered to your instance. All other ingress traffic will be discarded.You can

modify rules for a group at any time.The new rules are automatically enforced for all running instances

and instances launched in the future.

You can set up your Amazon EC2 security groups using the AWS Management Console or by using the

AWS Toolkit for Eclipse.You can specify which Amazon EC2 security groups control access to your

Elastic Beanstalk application by entering the names of one or more Amazon EC2 security group names

(delimited by commas) into the EC2 Security Groups box.

Note

If you are running your application using a legacy container type, make sure port 80 (HTTP) is

accessible from 0.0.0.0/0 as the source CIDR range if you want to enable health checks for your

application. For more information about health checks, see Health Checks (p. 117). To check if

you are using a legacy container type, see Why are some container types marked legacy? (p.426).

To create a security group using the AWS Toolkit for Eclipse

1. In the AWS Toolkit for Eclipse, click AWS Explorer tab. Expand the Amazon EC2 node, and then

double-click Security Groups.

2. Right-click anywhere in the left table, and then click New Group.

API Version 2010-12-01

114

Elastic Beanstalk Developer Guide

EC2 Server Instances

3. In the Security Group dialog box, type the security group name and description and then click OK.

For more information on Amazon EC2 Security Groups, see Using Security Groups in the Amazon Elastic

Compute Cloud User Guide.

Amazon EC2 Key Pairs

You can securely log in to the Amazon EC2 instances provisioned for your Elastic Beanstalk application

with an Amazon EC2 key pair.

Important

You must create an Amazon EC2 key pair and configure your Elastic Beanstalk-provisioned

Amazon EC2 instances to use the Amazon EC2 key pair before you can access your Elastic

Beanstalk-provisioned Amazon EC2 instances.You can create your key pair using the Publish

to Beanstalk Wizard inside AWS Toolkit for Eclipse when you deploy your application to Elastic

Beanstalk. Alternatively, you can set up your Amazon EC2 key pairs using the AWS Management

Console. For instructions on creating a key pair for Amazon EC2, see the Amazon Elastic

Compute Cloud Getting Started Guide.

For more information on Amazon EC2 key pairs, go to Using Amazon EC2 Credentials in the Amazon

Elastic Compute Cloud User Guide. For more information on connecting to Amazon EC2 instances, go

to Connecting to Instances and Connecting to a Linux/UNIX Instance from Windows using PuTTY in

the Amazon Elastic Compute Cloud User Guide.

CloudWatch Metrics

By default, only basic Amazon CloudWatch metrics are enabled; they return data in five-minute periods.

You can enable more granular one-minute CloudWatch metrics by selecting 1 minute for the Monitoring

Interval in the Server section of the Configuration tab for your environment in the AWS Toolkit for

Eclipse.

Note

Amazon CloudWatch service charges can apply for one-minute interval metrics. See Amazon

CloudWatch for more information.

Custom AMI ID

You can override the default AMI used for your Amazon EC2 instances with your own custom AMI by

entering the identifier of your custom AMI into the Custom AMI ID box in the Server section of the

Configuration tab for your environment in the AWS Toolkit for Eclipse.

Important

Using your own AMI is an advanced task and should be done with care. If you need a custom

AMI, we recommend you start with the default Elastic Beanstalk AMI and then modify it.To be

considered healthy, Elastic Beanstalk expects Amazon EC2 instances to meet a set of

requirements, including having a running host manager. If these requirements are not met, your

environment might not work properly.

API Version 2010-12-01

115

Elastic Beanstalk Developer Guide

EC2 Server Instances

Configuring Elastic Load Balancing Using AWS

Toolkit for Eclipse

Elastic Load Balancing is an Amazon web service that improves the availability and scalability of your

application.With Elastic Load Balancing, you can distribute application loads between two or more Amazon

EC2 instances. Elastic Load Balancing improves availability through redundancy, and it supports traffic

growth for your application.

Elastic Load Balancing automatically distributes and balances incoming application traffic among all the

EC2 server instances you are running.The service also makes it easy to add new instances when you

need to increase the capacity of your application.

Elastic Beanstalk automatically provisions Elastic Load Balancing when you deploy an application. Under

Load Balancing, on the Configuration tab for your environment inside the Toolkit for Eclipse, you can

edit the Elastic Beanstalk environment's load balancing configuration.

The following sections describe the Elastic Load Balancing parameters you can configure for your

application.

Ports

The load balancer provisioned to handle requests for your Elastic Beanstalk application sends requests

to the Amazon EC2 instances that are running your application.The provisioned load balancer can listen

for requests on HTTP and HTTPS ports and route requests to the Amazon EC2 instances in your AWS

Elastic Beanstalk application. By default, the load balancer handles requests on the HTTP port. At least

one of the ports (either HTTP or HTTPS) must be turned on.

Important

Make sure that the port you specified is not locked down; otherwise, users will not be able to

connect to your Elastic Beanstalk application.

API Version 2010-12-01

116

Elastic Beanstalk Developer Guide

Elastic Load Balancing

Controlling the HTTP port

To turn off the HTTP port, you select OFF for HTTP Listener Port. To turn on the HTTP port, you select

an HTTP port (for example, 80).

Note

If you want to access your environment using a different port other than the default port 80 (e.g.,

port 8080), you can add a listener to the existing load balancer and configure the new listener

to listen on that port. For example, using the Elastic Load Balancing API Tools, type the following

command replacing <yourloadbalancername> with the name of your load balancer for Elastic

Beanstalk.

elb-create-lb-listeners --lb <yourloadbalancername> --listener "pro

tocol=http, lb-port=8080, instance-port=80"

If you want Elastic Beanstalk to monitor your environment, do not remove the listener on port

80.

Controlling the HTTPS port

Elastic Load Balancing supports the HTTPS/TLS protocol to enable traffic encryption for client connections

to the load balancer. Connections from the load balancer to the EC2 instances are done using plain text.

By default, the HTTPS port is turned off.

To turn on the HTTPS port

1. Create and upload a certificate and key to the AWS Identity and Access Management (IAM) service.

The IAM service will store the certificate and provide an Amazon Resource Name (ARN) for the SSL

certificate you've uploaded. For more information on creating and uploading certificates, see the

Managing Server Certificates section of Using AWS Identity and Access Management.

2. Specify the HTTPS port by selecting a port from the HTTPS Listener Port drop-down list.

3. In the SSL Certificate ID text box, enter the Amazon Resources Name (ARN) of your SSL certificate

(e.g., arn:aws:iam::123456789012:server-certificate/abc/certs/build). Use the SSL

certificate that you created and uploaded in step 1. For information on viewing the certificate's ARN,

see Verify the Certificate Object topic in the Creating and Uploading Server Certificates section of

the Using IAM Guide.

To turn off the HTTPS port, select OFF for HTTPS Listener Port.

Health Checks

You can control the settings for the health check using the EC2 Instance Health Check section of the

Load Balancing panel.

The following list describes the health check parameters you can set for your application.

API Version 2010-12-01

117

Elastic Beanstalk Developer Guide

Elastic Load Balancing

• To determine instance health, Elastic Beanstalk looks for a 200 response code on a URL it queries.

By default, Elastic Beanstalk checks TCP:80 for nonlegacy containers and HTTP:80 for legacy containers.

You can override to match an existing resource in your application (e.g., /myapp/index.jsp) by

entering it in the Application Health Check URL box. If you override the default URL, Elastic Beanstalk

uses HTTP to query the resource.To check if you are using a legacy container type, see Why are some

container types marked legacy? (p. 426).

• For Health Check Interval (seconds), enter the number of seconds between your application's Amazon

EC2 instances health checks.

• For Health Check Timeout, specify the number of seconds for Elastic Load Balancing to wait for a

response before it considers an instance unresponsive.

• Use the Healthy Check Count Threshold and Unhealthy Check Count Threshold boxes, specify

the number of consecutive successful or unsuccessful URL probes before Elastic Load Balancing

changes the instance health status. For example, specifying 5 in the Unhealthy Check Count Threshold

text box means that the URL would have to return an error message or timeout five consecutive times

before Elastic Load Balancing considers the health check "failed."

Sessions

By default, a load balancer routes each request independently to the server instance with the smallest

load. By comparison, a sticky session binds a user's session to a specific server instance so that all

requests coming from the user during the session are sent to the same server instance.

Elastic Beanstalk uses load balancer–generated HTTP cookies when sticky sessions are enabled for an

application.The load balancer uses a special load balancer–generated cookie to track the application

instance for each request. When the load balancer receives a request, it first checks to see if this cookie

is present in the request. If so, the request is sent to the application instance specified in the cookie. If it

finds no cookie, the load balancer chooses an application instance based on the existing load balancing

algorithm. A cookie is inserted into the response for binding subsequent requests from the same user to

that application instance.The policy configuration defines a cookie expiry, which establishes the duration

of validity for each cookie.

Under Load Balancer in the Sessions section, specify whether or not the load balancer for your application

allows session stickiness and the duration for each cookie.

For more information on Elastic Load Balancing, go to the Elastic Load Balancing Developer Guide.

Configuring Auto Scaling Using AWS Toolkit for

Eclipse

Auto Scaling is an Amazon web service designed to automatically launch or terminate Amazon EC2

instances based on user-defined triggers. Users can set up Auto Scaling groups and associate triggers

with these groups to automatically scale computing resources based on metrics such as bandwidth usage

or CPU utilization. Auto Scaling works with Amazon CloudWatch to retrieve metrics for the server instances

running your application.

Auto Scaling lets you take a group of Amazon EC2 instances and set various parameters to have this

group automatically increase or decrease in number. Auto Scaling can add or remove Amazon EC2

instances from that group to help you seamlessly deal with traffic changes to your application.

API Version 2010-12-01

118

Elastic Beanstalk Developer Guide

Auto Scaling

Auto Scaling also monitors the health of each Amazon EC2 instance that it launches. If any instance

terminates unexpectedly, Auto Scaling detects the termination and launches a replacement instance.

This capability enables you to maintain a fixed, desired number of Amazon EC2 instances automatically.

Elastic Beanstalk provisions Auto Scaling for your application. Under Auto Scaling, on your environment's

Configuration tab inside the Toolkit for Eclipse, you can edit the Elastic Beanstalk environment's Auto

Scaling configuration.

The following sections discuss how to configure Auto Scaling parameters for your application.

Launch Configuration

You can edit the launch configuration to control how your Elastic Beanstalk application provisions Auto

Scaling resources.

Use the Minimum Instance Count and Maximum Instance Count settings to specify the minimum and

maximum size of the Auto Scaling group that your Elastic Beanstalk application uses.

Note

To maintain a fixed number of Amazon EC2 instances, set the Minimum Instance Count and

Maximum Instance Count text boxes to the same value.

For Availability Zones, specify the number of Availability Zones you want your Amazon EC2 instances

to be in. It is important to set this number if you want to build fault-tolerant applications: If one Availability

Zone goes down, your instances will still be running in your other Availability Zones.

Note

Currently, it is not possible to specify which Availability Zone your instance will be in.

API Version 2010-12-01

119

Elastic Beanstalk Developer Guide

Auto Scaling

Triggers

A trigger is an Auto Scaling mechanism that you set to tell the system when to increase (scale out) and

decrease (scale in) the number of instances.You can configure triggers to fire on any metric published

to Amazon CloudWatch, such as CPU utilization, and determine whether the specified conditions have

been met.When your upper or lower thresholds for the metric have been breached for the specified period

of time, the trigger launches a long-running process called a scaling activity.

You can define a scaling trigger for your Elastic Beanstalk application using the AWS Toolkit for Eclipse.

You can configure the following list of trigger parameters in the Scaling Trigger section of the

Configuration tab for your environment inside the Toolkit for Eclipse.

• For Trigger Measurement, specify the metric for your trigger.

• For Trigger Statistic, specify which statistic the trigger will use—Minimum, Maximum, Sum, or Average.

• For Unit of Measurement, specify the units for the trigger measurement.

• For Measurement Period, specify how frequently Amazon CloudWatch measures the metrics for your

trigger. For Breach Duration, specify the amount of time a metric can be beyond its defined limit (as

specified for Upper Threshold and Lower Threshold) before the trigger fires.

• For Scale-up Increment and Scale-down Increment, specify how many Amazon EC2 instances to

add or remove when performing a scaling activity.

For more information on Auto Scaling, go to the Auto Scaling documentation.

Configuring Notifications Using AWS Toolkit for

Eclipse

Elastic Beanstalk uses the Amazon Simple Notification Service (Amazon SNS) to notify you of important

events affecting your application.To enable Amazon SNS notifications, simply enter your email address

in the Email Address text box under Notifications on the Configuration tab for your environment inside

the Toolkit for Eclipse.To disable Amazon SNS notifications, remove your email address from the text

box.

API Version 2010-12-01

120

Elastic Beanstalk Developer Guide

Notifications

Configuring Java Containers Using AWS Toolkit

for Eclipse

The Container/JVM Options panel lets you fine-tune the behavior of the Java Virtual Machine on your

Amazon EC2 instances and enable or disable Amazon S3 log rotation.You can use the AWS Toolkit for

Eclipse to configure your container information.

Note

You can modify your configuration settings with zero downtime by swapping the CNAME for

your environments. For more information, see Deploying Versions with Zero Downtime (p. 318).

To access the Container/JVM Options panel for your Elastic Beanstalk application

1. If Eclipse isn't displaying the AWS Explorer view, in the menu click Window > Show View > AWS

Explorer. Expand the Elastic Beanstalk node and your application node.

2. In the AWS Explorer, double-click your Elastic Beanstalk environment.

3. At the bottom of the pane, click the Configuration tab.

4. Under Container, you can configure container options.

JVM Options

The heap size in the Java Virtual Machine affects how many objects can be created in memory before

garbage collection—a process of managing your application's memory—occurs.You can specify an initial

heap size and a maximum heap size. A larger initial heap size allows more objects to be created before

garbage collection occurs, but it also means that the garbage collector will take longer to compact the

heap. The maximum heap size specifies the maximum amount of memory the JVM can allocate when

expanding the heap during heavy activity.

You can set the initial and the maximum JVM heap sizes using the Initial JVM Heap Size (-Xms argument)

and Maximum JVM Heap Size (-Xmx argument) boxes.The available memory is dependent on the

Amazon EC2 instance type. For more information about the Amazon EC2 instance types available for

your Elastic Beanstalk environment, go to Instance Types in the Amazon EC2 User Guide.

The permanent generation is a section of the JVM heap that is used to store class definitions and

associated metadata.To modify the size of the permanent generation, type the new size in the Maximum

JVM PermGen Size (-XX:MaxPermSize argument) box.

Full documentation of JVM is beyond the scope of this guide; for more information on JVM garbage

collection, go to Java Garbage Collection Basics.

API Version 2010-12-01

121

Elastic Beanstalk Developer Guide

Containers

Amazon S3 Log Rotation

Elastic Beanstalk can copy the log files on an hourly basis for your application's Amazon EC2 instances

to the Amazon S3 bucket associated with your application.To enable this feature, select Enable log file

rotation to Amazon S3.

Remote Debugging

To test your application remotely, you can run your application in debug mode.

To enable remote debugging

1. Select Enable remote debugging.

2. For Remote debugging port, specify the port number to use for remote debugging.

The Additional Tomcat JVM command line options setting is filled automatically.

To start remote debugging

1. In the AWS Toolkit for Eclipse menu, click Window > Show View > Other.

2. Expand the Server folder, and then click Servers. Click OK.

3. In the Servers pane, right-click the server your application is running on, and then click Restart in

Debug.

Environment Properties

This section of the Container tab lets you specify environment properties on the Amazon EC2 instances

that are running your application. Environment properties are specific to your application environment

and are not actual (shell) environment variables. More specifically, PARAM1, PARAM2, etc. are system

properties passed into the JVM at startup using the -D flag.You can use them to pass database connection

strings, security credentials, or other information that you don't want to hard-code into your application.

Storing this information in environment properties can help increase the portability and scalability of your

application.You do not need to recompile your source code when you move between environments.You

can acquire them with System.getProperty(name). For more information on using and accessing

custom environment properties, see Using Custom Environment Properties with Elastic Beanstalk (p.102)

You can configure the following environment properties:

• Specify AWS credentials using the AWS_ACCESS_KEY_ID and AWS_SECRET_KEY boxes.

API Version 2010-12-01

122

Elastic Beanstalk Developer Guide

Containers

Note

For nonlegacy containers, use instance profiles so that your application can use temporary

security credentials to access AWS resources.To learn more, see Granting Permissions to

Users and Services Using IAM Roles (p. 562).

• Specify a connection string to an external database (such as Amazon RDS) by entering it in the

JDBC_CONNECTION_STRING box. For more information on how to set your

JDBC_CONNECTION_STRING, see Using Custom Environment Properties with Elastic

Beanstalk (p. 102).

• Specify up to five additional environment properties by entering them in the PARAM boxes.

Note

Environment properties can contain any printable ASCII character except the grave accent (`,

ASCII 96) and cannot exceed 200 characters in length.

Listing and Connecting to Server Instances

You can view a list of Amazon EC2 instances running your Elastic Beanstalk application environment

through the AWS Toolkit for Eclipse or from the AWS Management Console.You can connect to these

instances using Secure Shell (SSH). For information about listing and connecting to your server instances

using the AWS Management Console, see Listing and Connecting to Server Instances (p. 413). The

following section steps you through viewing and connecting you to your server instances using the AWS

Toolkit for Eclipse.

To view and connect to Amazon EC2 instances for an environment

1. In the AWS Toolkit for Eclipse, click AWS Explorer. Expand the Amazon EC2 node, and then

double-click Instances.

2. In the Amazon EC2 Instances window, in the Instance ID column, right-click the Instance ID for the

Amazon EC2 instance running in your application's load balancer. Then click Open Shell.

Eclipse automatically opens the SSH client and makes the connection to the EC2 instance.

For more information on connecting to an Amazon EC2 instance, see the Amazon Elastic Compute

Cloud Getting Started Guide.

Terminating an Environment

To avoid incurring charges for unused AWS resources, you can use the AWS Toolkit for Eclipse to

terminate a running environment.

API Version 2010-12-01

123

Elastic Beanstalk Developer Guide

Listing and Connecting to Server Instances

Note

You can always launch a new environment using the same version later.

To terminate an environment

1. In the AWS Toolkit for Eclipse, click the AWS Explorer pane. Expand the Elastic Beanstalk node.

2. Expand the Elastic Beanstalk application and right-click on the Elastic Beanstalk environment.

3. Click Terminate Environment. It will take a few minutes for Elastic Beanstalk to terminate the AWS

resources running in the environment.

Tools

AWS SDK for Java

With the AWS SDK for Java, you can get started in minutes with a single, downloadable package that

includes the AWS Java library, code samples, and documentation.You can build Java applications on

top of APIs to take the complexity out of coding directly against a web service interface. The library

provides APIs that hide much of the lower level plumbing, including authentication, request retries, and

error handling. Practical examples are provided for how to use the library to build applications.

In addition, with the AWS SDK for Java, you can use DynamoDB to share session states of Apache

Tomcat applications across multiple web servers. For more information, see Manage Tomcat Session

State with Amazon DynamoDB in the AWS SDK for Java documentation. For more information about the

AWS SDK for Java, go to http://aws.amazon.com/sdkforjava/.

AWS Toolkit for Eclipse

The AWS Toolkit for Eclipse is an open source plug-in for the Eclipse Java IDE that makes it easier to

develop and debug Java applications using Amazon Web Services, and now includes the Elastic Beanstalk

deployment feature.With the Elastic Beanstalk deployment feature, developers can use Eclipse to deploy

Java web applications to AWS Elastic Beanstalk and within minutes access their applications running on

AWS infrastructure services. The toolkit provides a Travel Log sample web application template that

demonstrates the use of Amazon S3 and Amazon SNS. For more information about the AWS Toolkit for

Eclipse, go to http://aws.amazon.com/eclipse.

Resources

There are several places you can go to get additional help when developing your Java applications.

DescriptionResource

Post your questions and get feedback.The AWS Java Development Forum

One-stop shop for sample code, documentation, tools, and

additional resources.

Java Developer Center

API Version 2010-12-01

124

Elastic Beanstalk Developer Guide

Creating and Deploying Elastic

Beanstalk Applications in .NET

Using AWS Toolkit for Visual

Studio

Topics

• Get Started (p. 126)

• Develop, Test, and Deploy (p. 134)

• Customizing and Configuring a .NET Environment (p. 150)

• Using Amazon RDS (p. 152)

• Managing Multiple Accounts (p. 154)

• Monitoring Application Health (p. 155)

• Viewing Events (p. 158)

• Managing Your Elastic Beanstalk Application Environments (p. 159)

• Listing and Connecting to Server Instances (p. 168)

• Terminating an Environment (p. 169)

• Tools (p. 170)

• Resources (p. 173)

Elastic Beanstalk for .NET makes it easier to deploy, manage, and scale your ASP.NET web applications

that use Amazon Web Services. Elastic Beanstalk for .NET is available to anyone who is developing or

hosting a web application that uses IIS.The first part of this topic presents instructions for creating, testing,

deploying, and redeploying your ASP.NET web application to Elastic Beanstalk using the AWS Toolkit

for Visual Studio.The second part explains how to manage and configure your applications and

environments using the AWS Toolkit for Visual Studio. For more information about prerequisites, installation

instructions, and running code samples, go to the AWS Toolkit for Microsoft Visual Studio. This site also

provides useful information about tools, how-to topics, and additional resources for ASP.NET developers.

If you are not a developer, but want to easily manage and configure your Elastic Beanstalk applications

and environments, you can use the AWS Management Console. For information, see Managing and

Configuring Applications and Environments Using the Console, CLI, and APIs (p. 278).

API Version 2010-12-01

125

Elastic Beanstalk Developer Guide

Get Started

This topic walks you through how to quickly get started deploying an open source ASP.NET application,

NerdDinner, using the AWS Toolkit for Visual Studio with Amazon Relational Database Service (Amazon

RDS) using Microsoft Visual Studio 2010 (Professional Edition). NerdDinner is an application that helps

people host lunches, dinners, and informal get-togethers.To deploy NerdDinner, you will do the following

steps:

1. Step 1: Set Up the NerdDinner Application (p. 126)

2. Step 2: Launch an Amazon RDS DB Instance (p. 127)

3. Step 3: Set Up the NerdDinner Database (p. 128)

4. Step 4: Deploy to Elastic Beanstalk (p. 131)

Note

This walkthrough has been tested and is supported using Microsoft Visual Studio 2010

(Professional Edition).

Video available

Note

This example uses Amazon RDSs, and you may be charged for its usage. For more information

about pricing, go to Amazon Relational Database Service (RDS) Pricing. If you are a new

customer, you can make use of the AWS Free Usage Tier. For details, go to AWS Free Usage

Tier.

Step 1: Set Up the NerdDinner Application

In this step, you'll download and open NerdDinner inside Visual Studio, and then script the NerdDinner

database to later recreate the database for Amazon RDS. For this example, we use NerdDinner 2.0. If

you haven't already installed the AWS Toolkit for Visual Studio, do that now. For prerequisite and installation

information, go to AWS Toolkit for Microsoft Visual Studio.

To open NerdDinner project in Microsoft Visual Studio

1. Download NerdDinner from http://nerddinner.codeplex.com/, and extract the files to your local

computer.

2. In Visual Studio, on the File menu, click Open, and then click Project. Navigate to the NerdDinner

project, and click Open.

To script the NerdDinner database

1. In Server Explorer, right-click Data Connections, and then click Add Connection.

2. In the Add Connection dialog box, click Change, and then click Microsoft SQL Server Database

File. Click OK.

3. Click Browse next to the Database file name box, and select the NerdDinner.mdf file located in

the NerdDinner/App_Data directory. Click Open.

4. In Server Explorer, right-click NerdDinner.mdf, and click Publish to provider.

5. In the Database Publishing wizard, click Next twice. On the Select an Output Location page, note

the path and file name in the File name box.You will need this for later.

6. Click Finish twice to accept all defaults in the wizard.

API Version 2010-12-01

126

Elastic Beanstalk Developer Guide

Get Started

Step 2: Launch an Amazon RDS DB Instance

Next, you'll want to launch your Amazon RDS database instance because it will take a few minutes to

set up.

To launch an Amazon RDS database

1. In Visual Studio on the View menu, click AWS Explorer.

2. Expand Amazon RDS. Right-click DB Instances, and then click Launch DB Instance.

3. On the DB Engine Selection page in the Launch DB Instance wizard, select a database engine.

Microsoft SQL Server Express Edition is eligible for the Amazon RDS for SQL Server – Free Usage

Tier. For more information, go to Amazon RDS Free Usage Tier. For this example, select sqlserver-ex,

and then click Next.

4. On the DB Engine Instance Options page, do the following, and then click Finish to accept the

default values in the rest of the wizard.Your database instance will appear under the DB Instances

node in Visual Studio.

• In the DB Instance Class list, select the type of database you want. The db.t1.micro is eligible

for the Amazon RDS for SQL Server – Free Usage Tier when used with Microsoft SQL Server

Express Edition. For more information, go to Amazon RDS Free Usage Tier.

• For DB Instance Identifier, type demodb.The DB Instance Identifier is a name for your DB Instance

that is unique for your account in a region.

• For Master User Name, type the name you will use to log on to your DB Instance with all database

privileges.

• For Master User Password, type a password for your master user.

API Version 2010-12-01

127

Elastic Beanstalk Developer Guide

Step 2: Launch an Amazon RDS DB Instance

Step 3: Set Up the NerdDinner Database

To set up the NerdDinner database, you'll need to do the following steps:

1. Create a SQL DB.

2. Update your DB connection string.

3. Connect to the database.

4. Close the connection to the NerdDinner database.

To create a SQL DB

1. When the Amazon RDS database is in the available state, right-click the DB instance, and then click

Create SQL DB.

Note

To check if your database is in the available state, right-click the DB instance, and then click

View. Ensure that the Status column says available.

2. The toolkit needs to add permissions to the Amazon RDS security group so that your computer can

connect to the SQL database. In the Unable to Connect dialog box, click OK.

API Version 2010-12-01

128

Elastic Beanstalk Developer Guide

Step 3: Set Up the NerdDinner Database

3. In the Create SQL Server Database dialog box, type the user name, password, and name for your

database, and then click OK. The database now appears in Server Explorer.

To update your connection string

1. In Server Explorer, click the Amazon RDS database, and copy the connection string from the

Properties window.

2. In Solution Explorer, open the ConnectionStrings.config file.

3. For NerdDinnerEntities, update the embedded connection string by replacing the data source

in the provider connection string with your Amazon RDS connection string as in the following example.

Data Source=<Your RDS endpoint>,1433;Initial Catalog=mydb;User

ID=awsuser;Password=***********

To connect to your database

1. In Visual Studio, open the file NerdDinner.mdf.mysql. Navigate to the path and file name you

wrote down when you scripted the NerdDinner database in Step 1: Set Up the NerdDinner

Application (p. 126).

API Version 2010-12-01

129

Elastic Beanstalk Developer Guide

Step 3: Set Up the NerdDinner Database

2. On the toolbar, click the Connect icon.

3. In the Connect to Database Engine dialog box, in the Server name box, type or paste the Amazon

RDS endpoint.

Note

To get the Amazon RDS endpoint, click the Amazon RDS DB Instance, and copy the endpoint

from the Properties window.

4. Click Options, and for Database name, type the name of your database. In this example, we used

mydb.The name of the NerdDinner.MDF.sql tab will now contain the name of the Amazon RDS

endpoint.

5. On the toolbar, click the Execute SQL icon.You will see the message Command(s) completed

successfully under the Messages tab.

6. To verify everything worked correctly, in Server Explorer, expand the Amazon RDS database, and

then expand the Tables node.You should now see Dinners and RSVP.

Before you deploy to Elastic Beanstalk, close the connection to the NerdDinner database.

To close the connection to the NerdDinner database

1. In Visual Studio, in Server Explorer, expand Data Connections. Right-click NerdDinner.mdf.

2. Click Close Connection.

API Version 2010-12-01

130

Elastic Beanstalk Developer Guide

Step 3: Set Up the NerdDinner Database

Step 4: Deploy to Elastic Beanstalk

After configuring your NerdDinner application to connect to your Amazon RDS database, you are ready

to deploy your application to Elastic Beanstalk.

To deploy your application to Elastic Beanstalk using the AWS Toolkit for Visual Studio

1. In Solution Explorer, right-click your application and then select Publish to AWS.

2. Select a template.

a. In the AWS account to use for deployment list, click your account, or click the Add another

account icon to enter new account information.

b. In the Region list, click the region where you want to deploy your application. For information

about this product's regions, go to Regions and Endpoints in the Amazon Web Services General

Reference. If you select a region that is not supported by Elastic Beanstalk, then the option to

deploy to Elastic Beanstalk will become unavailable.

c. Select Deploy new application with template text box and click Elastic Beanstalk.Then click

Next.

3. For Name, type the name of the application, and then click Next.

API Version 2010-12-01

131

Elastic Beanstalk Developer Guide

Step 4: Deploy to Elastic Beanstalk

4. On the Environment page, do the following:

a. For Name, type a name for your environment.

b. Keep the Type as Load balanced, auto scaled.

c. Click Check availability to make sure the environment URL is available.

d. Click Next twice to accept the default settings and skip to the Amazon RDS Database Security

Group page.

5. If you want to connect your AWS Elastic Beanstalk environment to your Amazon RDS database

instance, select the RDS Database security group associated with your database instance. Click

Finish, and then click Deploy. It will take a few minutes for Elastic Beanstalk to deploy your

application.

API Version 2010-12-01

132

Elastic Beanstalk Developer Guide

Step 4: Deploy to Elastic Beanstalk

6. To check the status of your environment, in AWS Explorer, right-click your Elastic Beanstalk

environment, and then click View Status.When your status says Environment is healthy, you can

view your application.

7. To view your application, in the Elastic Beanstalk environment tab, click the URL shown in the previous

illustration. Log in and host a dinner!

API Version 2010-12-01

133

Elastic Beanstalk Developer Guide

Step 4: Deploy to Elastic Beanstalk

Note

By default, at least one Amazon EC2 instance is launched as part of your Auto Scaling

group. If more than one instance is launched (e.g., due to an increase in traffic load), we

recommend enabling session stickiness when deploying NerdDinner.Your load balancer

makes a user’s session “sticky” by binding it to a specific server instance so that all requests

coming from the user during the session will be sent to the same server instance. For

information about how to enable session stickiness, see Sessions (p. 361).

Develop,Test, and Deploy

Topics

• Create a Project (p. 135)

• Test Locally (p. 135)

• Deploy to AWS Elastic Beanstalk (p. 136)

• Debug/View Logs (p. 143)

• Edit the Application and Redeploy (p. 143)

• Deploy to Production (p. 144)

• Deploy an Existing Application Version to an Existing Environment (p. 149)

The following diagram of a typical software development life cycle includes deploying your application to

Elastic Beanstalk.

API Version 2010-12-01

134

Elastic Beanstalk Developer Guide

Develop,Test, and Deploy

After developing and testing your application locally, you will typically deploy your application to AWS

Elastic Beanstalk. After deployment, your application will be live at a URL such as

http://myexampleapp-wpams3yrvj.elasticbeanstalk.com. Because your application is live, you should

consider setting up multiple environments, such as a testing environment and a production environment.

You can use the AWS Toolkit for Visual Studio if you want to set up different AWS accounts for testing,

staging, and production. For more information about managing multiple accounts, see Managing Multiple

Accounts (p. 154).

Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service.You can

point your domain name to the Amazon Route 53 CNAME <yourappname>.elasticbeanstalk.com. Contact

your DNS provider to set this up. For information about how to map your root domain to your Elastic Load

Balancer, see Using Elastic Beanstalk with Amazon Route 53 to Map Your Domain to Your Load

Balancer (p. 528).

After you remotely test and debug your Elastic Beanstalk application, you can make any updates and

then redeploy to Elastic Beanstalk. After you are satisfied with all of your changes, you can upload the

latest version to your production environment.The following sections explain each stage of the software

development life cycle.

Create a Project

Visual Studio provides templates for different programming languages and application types.You can

start with any of these templates.The AWS Toolkit for Visual Studio also provides three project templates

that bootstrap development of your application: AWS Console Project, AWS Web Project, and AWS

Empty Project. For this example, you'll create a new ASP.NET Web Application.

To create a new ASP.NET Web Application project

1. In Visual Studio, on the File menu, click New and then click Project.

2. In the New Project dialog box, click Installed Templates, click Visual C#, and then click Web. Click

ASP.NET Empty Web Application, type a project name, and then click OK.

To run a project

Do one of the following:

• Press F5.

• Select Start Debugging from the Debug menu.

Test Locally

Visual Studio makes it easy for you to test your application locally.To test or run ASP.NET web applications,

you need a web server. Visual Studio offers several options, such as Internet Information Services (IIS),

API Version 2010-12-01

135

Elastic Beanstalk Developer Guide

Create a Project

IIS Express, or the built-in Visual Studio Development Server. To learn about each of these options and

to decide which one is best for you, go to Web Servers in Visual Studio for ASP.NET Web Projects .

Deploy to AWS Elastic Beanstalk

After testing your application, you are ready to deploy it to Elastic Beanstalk.

To deploy your application to Elastic Beanstalk using the AWS Toolkit for Visual Studio

1. In Solution Explorer, right-click your application and then select Publish to AWS.

2. In the Publish to AWS wizard, enter your account information.

a. For AWS account to use for deployment, select your account or select Other to enter new

account information.

b. For Region, select the region where you want to deploy your application. For information about

this product's regions, go to Regions and Endpoints in the Amazon Web Services General

Reference. If you select a region that is not supported by Elastic Beanstalk, then the option to

deploy to Elastic Beanstalk will become unavailable.

c. Click Deploy new application with template and select Elastic Beanstalk.Then click Next.

3. On the Application page, enter your application details.

a. For Name, type the name of the application.

b. For Description, type a description of the application. This step is optional.

c. The version label of the application automatically appears in the Deployment version label

d. Select Deploy application incrementally to deploy only the changed files. An incremental

deployment is faster because you are updating only the files that changed instead of all the files.

If you choose this option, an application version will be set from the Git commit ID. If you choose

API Version 2010-12-01

136

Elastic Beanstalk Developer Guide

Deploy to AWS Elastic Beanstalk

to not deploy your application incrementally, then you can update the version label in the

Deployment version label box.

e. Click Next.

4. On the Environment page, describe your environment details.

a. Select Create a new environment for this application.

b. For Name, type a name for your environment.

c. For Description, characterize your environment.This step is optional.

d. Select the Type of environment that you want.

You can select either Load balanced, auto scaled or a Single instance environment. For more

information, see Environment Types (p. 345).

Note

For single-instance environments, load balancing, autoscaling, and the health check

URL settings don't apply.

e. The environment URL automatically appears in the Environment URL once you move your

cursor to that box.

f. Click Check availability to make sure the environment URL is available.

g. Click Next.

5. On the AWS Options page, configure additional options and security information for your deployment.

API Version 2010-12-01

137

Elastic Beanstalk Developer Guide

Deploy to AWS Elastic Beanstalk

a. For Container Type, select 64bit Windows Server 2012 running IIS 8 or 64bit Windows

Server 2008 running IIS 7.5.

b. For Instance Type, select Micro.

c. For Key pair, select Create new key pair. Type a name for the new key pair—in this example,

we use myuswestkeypair—and then click OK. A key pair enables remote-desktop access to

your Amazon EC2 instances. For more information on Amazon EC2 key pairs, see Using

Credentials in the Amazon Elastic Compute Cloud User Guide.

d. Select an instance profile.

If you are using a nonlegacy container, you have the option to select an instance profile. If you

are using a legacy container, this option does not appear in the dialog box. An instance profile

provides applications and services access to AWS resources using temporary security credentials.

For example, if your application requires access to Amazon DynamoDB, it must use AWS security

credentials to make an API request.The application can use the temporary security credentials

so you do not have to store long-term credentials on an EC2 instance or update the EC2 instance

every time the credentials are rotated. In addition, Elastic Beanstalk requires an instance profile

to rotate logs to Amazon S3.The Instance Profile list displays the profiles available for your

Elastic Beanstalk environment. If you do not have an instance profile, you can select Create a

default instance profile. Elastic Beanstalk creates a default instance profile and updates the

Amazon S3 bucket policy to allow log rotation. If you choose to not use the default instance

profile, you need to grant permissions for Elastic Beanstalk to rotate logs. For instructions, see

Using a Custom Instance Profile (p. 577). For more information about log rotation, see Elastic

Beanstalk Environment Configurations (p.389). For more information about using instance profiles

with Elastic Beanstalk, see Using IAM Roles with Elastic Beanstalk (p. 568).

Note

Users must have permission to create a default profile. For more information, see

Granting IAM Users Permissions to Create and Pass IAM Roles (p. 568).

e. If you are using a nonlegacy container, you have the option to create your environment inside

an existing VPC; to do this, click Launch into VPC.You can configure the VPC information on

the next page. For more information about Amazon VPC, go to Amazon Virtual Private Cloud

(Amazon VPC). For a list of supported nonlegacy container types, see Why are some container

types marked legacy? (p. 426).

API Version 2010-12-01

138

Elastic Beanstalk Developer Guide

Deploy to AWS Elastic Beanstalk

f. Click Next.

6. If you selected to launch your environment inside a VPC, the VPC Options page appears; otherwise,

the Additional Options page appears. Here you'll configure your VPC options.

API Version 2010-12-01

139

Elastic Beanstalk Developer Guide

Deploy to AWS Elastic Beanstalk

VPC options for load-balanced, autoscaled environment

VPC options for single-instance environment

a. Select the VPC ID of the VPC in which you would like to launch your environment.

API Version 2010-12-01

140

Elastic Beanstalk Developer Guide

Deploy to AWS Elastic Beanstalk

Note

If you do not see the VPC information, then you have not created a VPC in the same

region in which you are launching your environment.To learn how to create a VPC,

see Using Elastic Beanstalk with Amazon VPC (p. 531).

b. For a load-balanced, autoscaled environment, select private for ELB Scheme if you do not

want your elastic load balancer to be available to the Internet.

For a single-instance environment, this option is not applicable because the environment doesn't

have a load balancer. For more information, see Environment Types (p. 345).

c. For a load-balanced, autoscaled environment, select the subnets for the elastic load balancer

and the EC2 instances. If you created public and private subnets, make sure the elastic load

balancer and the EC2 instances are associated with the correct subnet. By default, Amazon

VPC creates a default public subnet using 10.0.0.0/24 and a private subnet using 10.0.1.0/24.

You can view your existing subnets in the Amazon VPC console at https://

console.aws.amazon.com/vpc/.

For a single-instance environment, your VPC only needs a public subnet for the instance.

Selecting a subnet for the load balancer is not applicable because the environment doesn't have

a load balancer. For more information, see Environment Types (p. 345).

d. For a load-balanced, autoscaled environment, select the VPC security group for your NAT

instance. For instructions on how to create this security group and update your default VPC

security group, see Step 2: Configure the Default VPC Security Group for the NAT

Instance (p. 539).

For a single-instance environment, you don't need a NAT. Select the default security group.

Elastic Beanstalk assigns an Elastic IP address to the instance that lets the instance access the

Internet.

e. Click Next.

7. On the Application Options page, configure your application options.

a. For Target framework, select .NET Frameworke 4.0.

b. Elastic Load Balancing uses a health check to determine whether the Amazon EC2 instances

running your application are healthy.The health check determines an instance's health status

by probing a specified URL at a set interval.You can override the default URL to match an

existing resource in your application (e.g., /myapp/index.aspx) by entering it in the Application

health check URL box. For more information about application health checks, see Health

Checks (p. 362).

c. Type an email address if you want to receive Amazon Simple Notification Service (Amazon

SNS) notifications of important events affecting your application.

d. The Application Environment section lets you specify environment variables on the Amazon

EC2 instances that are running your application.This setting enables greater portability by

eliminating the need to recompile your source code as you move between environments.

e. Select the application credentials option you want to use to deploy your application.

API Version 2010-12-01

141

Elastic Beanstalk Developer Guide

Deploy to AWS Elastic Beanstalk

f. Click Next.

8. If you have previously set up an Amazon RDS database, the Amazon RDS DB Security Group

page appears. If you want to connect your Elastic Beanstalk environment to your Amazon RDS DB

Instance, then select one or more security groups. Otherwise, go on to the next step. When you're

ready, click Next.

9. Review your deployment options. If everything is as you want, click Deploy.

API Version 2010-12-01

142

Elastic Beanstalk Developer Guide

Deploy to AWS Elastic Beanstalk

Your ASP.NET project will be exported as a web deploy file, uploaded to Amazon S3, and registered

as a new application version with Elastic Beanstalk.The Elastic Beanstalk deployment feature will

monitor your environment until it becomes available with the newly deployed code. On the

env:<environment name> tab, you will see status for your environment.

Debug/View Logs

To investigate any issues, you can view logs. For information about viewing logs, see Working with

Logs (p. 415). If you need to test remotely, you can connect to your EC2 instances. For instructions on

how to connect to your instance, see Listing and Connecting to Server Instances (p. 413).

Edit the Application and Redeploy

Now that you have tested your application, it is easy to edit and redeploy your application and see the

results in moments.

To edit and redeploy your ASP.NET web application

1. In Solution Explorer, right-click your application, and then click Republish to Environment <your

environment name>.The Re-publish to AWS Elastic Beanstalk wizard opens.

API Version 2010-12-01

143

Elastic Beanstalk Developer Guide

Debug/View Logs

2. Review your deployment details and click Deploy.

Note

If you want to change any of your settings, you can click Cancel and use the Publish to

AWS wizard instead. For instructions, see Deploy to AWS Elastic Beanstalk (p. 136).

Your updated ASP.NET web project will be exported as a web deploy file with the new version label,

uploaded to Amazon S3, and registered as a new application version with Elastic Beanstalk.The

Elastic Beanstalk deployment feature monitors your existing environment until it becomes available

with the newly deployed code. On the env:<environment name> tab, you will see the status of

your environment.

Deploy to Production

When you are satisfied with all of the changes you want to make to your application, you can deploy your

application version to your production environment.

To deploy an application version to production

1. Right-click your Elastic Beanstalk application by expanding the Elastic Beanstalk node in AWS

Explorer. Select View Status.

2. In the App: <application name> tab, click Versions.

3. Click the application version you want to deploy and click Publish Version.The Publish Application

Version wizard appears.

API Version 2010-12-01

144

Elastic Beanstalk Developer Guide

Deploy to Production

4. Describe your environment details.

a. Select the Create a new environment for this application button.

b. In the Name box, type a name for your environment name.

c. In the Description box, type a description for your environment. This step is optional.

d. The environment URL is auto-populated in the Environment URL box.

e. Click Check availability to make sure the environment URL is available.

f. Click Next. The AWS Options page appears.

5. Configure additional options and security information for your deployment.

API Version 2010-12-01

145

Elastic Beanstalk Developer Guide

Deploy to Production

a. In the Container Type list, click 64bit Windows Server 2012 running IIS 8 or 64bit Windows

Server 2008 running IIS 7.5.

b. In the Instance Type list, click Micro.

c. In the Key pair list, click Create new key pair.Type a name for the new key pair—in this

example, we use my example key pair—and then click OK. A key pair enables you to remote

desktop into your Amazon EC2 instances. For more information on Amazon EC2 key pairs, see

Using Credentials in the Amazon Elastic Compute Cloud User Guide.