The following macros are not currently supported in the header:
  • unmigrated-wiki-markup

Documentation for Tasks for AWS 2.8 – other releases are available in the Tasks for AWS Documentation Directory.
View

Unknown macro: {spacejump}

or visit the current documentation home.

Deploying to AWS Elastic Beanstalk

Owned by Steffen Opel [Utoolity]
Last updated: 28.10.2015 by Henrik Opel [Utoolity]Version comment
2 min read

Components

The deployment of an artifact to AWS Elastic Beanstalk involves several major components as follows:

  • Application – a logical collection of Elastic Beanstalk components, including environments, versions [...] (see the next two)
  • Application Version – a specific, labeled iteration of deployable code for a web application
  • Environment – a version that is deployed onto AWS resources

 

 

On this page:

Related Pages:

Workflow

The deployment workflow is illustrated by the diagram in What Is AWS Elastic Beanstalk and Why Do I Need It?:

The binding between those components is established indirectly and comprises the following activities:

  1. create an application – see the Create Application action of the AWS Elastic Beanstalk Application task
  2. upload the application source code (the 'Source Bundle') – see the Upload File(s) action of the Amazon S3 Object task
  3. create an application version for that application – see the Create Application Version action of the AWS Elastic Beanstalk Application Version task
  4. launch an environment with one of the available application versions of an application – see the Create Environment action of the AWS Elastic Beanstalk Environment task
  5. manage the environment, which implies going back to 3./4. and selecting one of two approaches for deploying a new application version (be it a newly created or a former one):
    1. update an environment as outlined in Deploying Versions to Existing Environments by replacing the currently running application version with another one – see the Update Environment action of the AWS Elastic Beanstalk Environment task
    2. create a new environment, optionally swapping over to that one by Deploying Versions with Zero Downtime once it is verified as working correctly – see the Swap Environment CNAMEs action of the AWS Elastic Beanstalk Environment task

Alternative workflow via CloudFormation

As an alternative to using the AWS Elastic Beanstalk tasks built into Tasks for AWS, it is also possible to provision the Elastic Beanstalk components directly via the AWS CloudFormation Stack task and the corresponding CloudFormation resource types:

A typical workflow based on CloudFormation might look as follows:

  1. upload the application source code (the 'Source Bundle') – see the Upload File(s) action of the Amazon S3 Object task
  2. create/update the CloudFormation stack that provisions the Elastic Beanstalk application, application version and environment – see the Create Stack action of the AWS CloudFormation Stack task
    1. (lightbulb) You can use the Update stack, if it already exists option to reuse the same Bamboo job for both actions

Frequently Asked Questions (FAQ)