- unmigrated-wiki-markup
Documentation for Tasks for AWS 2.5 – other releases are available in the Tasks for AWS Documentation Directory.
View
or visit the current documentation home.
Using the AWS Elastic Beanstalk Environment task in Bamboo
- Steffen Opel [Utoolity]
You can use the Elastic Beanstalk Environment task to create, update, rebuild, restart, swap or terminate an AWS Elastic Beanstalk environment (see Deploying to AWS Elastic Beanstalk for an overview of the Elastic Beanstalk component lifecycle and deployment workflow).
Configuration
Docker Support
You can also deploy AWS Elastic Beanstalk applications from Docker containers - select an appropriate solution stack from Configuration Source as follows:
- Docker - this supports a workflow based on your own Docker containers, refer to Dockerfile and Dockerrun.aws.json for details.
- <platform> (Preconfigured Docker) - this supports a workflow based on Docker containers preconfigured from base images provided in the Docker Hub Registry at Repositories, refer to Deploying AWS Elastic Beanstalk Applications from Preconfigured Docker Containers for details.
Deployment Cycle
The required Version Label stems from an Application Version previously provisioned - assuming an Application already exists, the typical deployment cycle is as follows:
- upload a source bundle via the S3 Object task's Upload action
- create a version via the Elastic Beanstalk Application Version task's Create action
- deploy that version via the Elastic Beanstalk Environment task's Update action
To configure an AWS Elastic Beanstalk Environment task:
- Navigate to the Tasks configuration tab for the job (this will be the default job if creating a new plan).
- Click the name of an existing AWS Elastic Beanstalk Environment task, or click Add Task and then AWS Elastic Beanstalk Environment to create a new task.
Complete the following settings:
Common to all tasks
Task Description (Optional) Identify the purpose of the task. Disable this task Check, or clear, to selectively run this task.
Action Each task supports one or more actions depending on the target AWS resource. Select the desired action and configure the action specific parameters below.
Region Select the desired AWS Region from the preconfigured list. Alternatively, select [Use region variable ...] to supply the region dynamically via Bamboo variables for example (needs to be a region code such as ap-southeast-2) .... Configure task/action specific parameters, see below ... AWS Credentials Source Select the source for the required AWS Security Credentials - can be either Inline, an IAM Role for EC2 or a shared Identity Federation for AWS Connector. Actions supported by this task:
Create
Application Name Specify the name of the application that contains the version to be deployed
Environment Name Specify an environment name.
Must be unique within your account. If the name already exists, the task will fail.
Environment Tier Select a Web Server or Worker environment tier.
- Refer to the Architectural Overview for the differences between these environment tier types.
Version Label (Optional) Specify the label of the application version to deploy.
- If not specified, AWS Elastic Beanstalk attempts to launch the sample application in the container.
CNAME Prefix (Optional) Specify the prefix for the CNAME that the environment should attempt to use.
- Must be unique across all Elastic Beanstalk environments. If the name already exists, the task will fail.
If not specified, the CNAME is generated automatically by appending a random alphanumeric string to the environment name.
Configuration Source Select a predefined solution stack or saved named template.
- There might be more recent solution stacks available, see Supported Platforms – you can enter an updated version manually.
Advanced Options Await Health Status Timeout Specify how long to await the environment's health status reaching a non grey state (seconds, 0 to skip). Verify Green Health Status Period Specify how long to verify the environment's health status being green (seconds, 0 to skip)? Configuration Option Settings (Optional) Configure the environment's option settings.
- Refer to Option Values for available configuration option settings.
Tags (Optional) Tag the environment.
Refer to Tagging Your Amazon EC2 Resources and Listing and Filtering Your Resources for details. For example:
- Single Instance – Uses single-instance environment type instead of load-balanced.
- Instance type – Sets the configurations instance type to the desired size/type.
- Auto Scaling range – Sets the Auto Scaling group instance number min and max sizes.
- Worker Tier IAM Profile – Defines the IAM instance profile to use for a worker tier configuration.
- General Purpose (SSD) storage volume – Defines the root storage volume for the Amazon EC2 instances in the environment as general purpose SSD.
Description (Optional) Describe the environment. Update
Environment Name or ID or CNAME Specify the target environment. You can use its name, ID or the associated CNAME.
- CNAME needs to be the fully qualified domain name, e.g. "someEnv.elasticbeanstalk.com"
Version Label see Create above
Advanced Options Await Health Status Timeout see Create above Verify Green Health Status Period see Create above Configuration Option Settings see Create above
Tags see Create above Description see Create above Rebuild
Environment Name or ID or CNAME see Update above Advanced Options Await Health Status Timeout see Create above Verify Green Health Status Period see Create above Restart
Environment Name or ID or CNAME see Update above Advanced Options Await Health Status Timeout see Create above Verify Green Health Status Period see Create above Swap
The Swap action enables Deploying Versions with Zero Downtime by swapping the URLs between two environments - this concept is also referred to as a Blue-Green deployments.
Source Environment Name or ID or CNAME Specify the source environment. You can use its name, ID or the associated CNAME.
- CNAME needs to be the fully qualified domain name, e.g. "someEnv.elasticbeanstalk.com"
Destination Environment Name or ID Specify the target environment. You can use its name or ID. Terminate
Environment Name or ID or CNAME see Update above
Terminate Resources Check to also terminate the associated AWS resources. Clear to remove the associated AWS resources from Elastic Beanstalk, but continue to operate them.