Using the Amazon ECS Cluster task in Bamboo

Using the Amazon ECS Cluster task in Bamboo

You can use the Amazon ECS Cluster task to create or delete an Amazon Elastic Container Service (ECS) cluster (see Deploying to Amazon ECS for an overview of the ECS component lifecycle and deployment workflow).

 



Configuration

Cluster Management

While useful for end to end automation and test scenarios, it is quite common to create ECS Clusters e.g. via the AWS Management Console upfront and only manage ECS Task Definitions, Tasks and Services from your build and deployment projects.

To configure an Amazon ECS Cluster task:

1. Navigate to the Tasks configuration tab for the job (this will be the default job if creating a new plan).

2. Click the name of an existing Amazon ECS Cluster task, or click Add Task and then Amazon ECS Cluster to create a new task.

3. Complete the following settings:

a. Common to all tasks

 Click here to expand...

Common (Bamboo)


Task Description (Optional) Identify the purpose of the task.
Disable this task

Check, or clear, to selectively run this task.

...Configure task/action specific parameters, see below ...
Bamboo Variables
NamespaceProvide the namespace for generated variables – defaults to custom.aws for backward compatibility.
Scope

Select the scope for generated variables – can be either Local (Variables will only be available in this job), or Result (Variables will be available in subsequent plan stages and deployment releases).

Common (AWS)


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.

RegionSelect the desired AWS Region. Alternatively, select [Use region variable ...] to supply the region dynamically via Bamboo variables (needs to be a region code such as ap-southeast-2) - refer to How to parametrize the AWS region via a Bamboo variable for details.
...Configure task/action specific parameters, see below ...
AWS Security Credentials
SourceSelect 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.
Connector(Conditional) Select the shared Identity Federation for AWS Connector. Alternatively, select [Use connector variable ...] to supply the connector dynamically via Bamboo variables (needs to be a connector id such as f24e81bc-7aff-42db-86a2-7cf82e24d871) - refer to How to parametrize the AWS connector via a Bamboo variable for details.

b. Actions supported by this task:



Create Cluster



Create Cluster



Cluster Name

(Optional) Specify the cluster name.

  • If you do not specify a name for your cluster, you will create a cluster named default

  • This name must be unique within your account. If the specified name already exists, the task will fail.

Tags

Specify the tags to apply (JSON – inline or via URL).

Delete Cluster



Cluster Name or ARN

Specify the cluster name or Amazon Resource Name (ARN).



Variables

All tasks support Bamboo Variable Substitution/Definition - this task's actions generate variables as follows:

A task's generated variables might get amended with respective AWS API additions over time - a live build log will always provide the most current variable shape accordingly

Create Cluster

Creating common variables for 1 resources affected by task: ... bamboo.custom.aws.ecs.cluster.resources: TAWS-IT270-ECSC-43-ubot Creating resource variables for cluster 'TAWS-IT270-ECSC-43-ubot': ... bamboo.custom.aws.ecs.cluster.resources.TAWS-IT270-ECSC-43-ubot.ClusterName: TAWS-IT270-ECSC-43-ubot ... bamboo.custom.aws.ecs.cluster.resources.TAWS-IT270-ECSC-43-ubot.ClusterARN: arn:aws:ecs:us-east-1:309600995652:cluster/TAWS-IT270-ECSC-43-ubot ... bamboo.custom.aws.ecs.cluster.resources.TAWS-IT270-ECSC-43-ubot.Status: ACTIVE ... bamboo.custom.aws.ecs.cluster.resources.TAWS-IT270-ECSC-43-ubot.ActiveServicesCount: 0 ... bamboo.custom.aws.ecs.cluster.resources.TAWS-IT270-ECSC-43-ubot.PendingTasksCount: 0 ... bamboo.custom.aws.ecs.cluster.resources.TAWS-IT270-ECSC-43-ubot.RunningTasksCount: 0 ... bamboo.custom.aws.ecs.cluster.resources.TAWS-IT270-ECSC-43-ubot.RegisteredContainerInstancesCount: 0 Creating common variables for first resource affected by task: Creating resource variables for cluster 'TAWS-IT270-ECSC-43-ubot': ... bamboo.custom.aws.ecs.cluster.first.ClusterName: TAWS-IT270-ECSC-43-ubot ... bamboo.custom.aws.ecs.cluster.first.ClusterARN: arn:aws:ecs:us-east-1:309600995652:cluster/TAWS-IT270-ECSC-43-ubot ... bamboo.custom.aws.ecs.cluster.first.Status: ACTIVE ... bamboo.custom.aws.ecs.cluster.first.ActiveServicesCount: 0 ... bamboo.custom.aws.ecs.cluster.first.PendingTasksCount: 0 ... bamboo.custom.aws.ecs.cluster.first.RunningTasksCount: 0 ... bamboo.custom.aws.ecs.cluster.first.RegisteredContainerInstancesCount: 0

Delete Cluster

N/A

How-to Articles

Atlassian®, Atlassian Bamboo®, Bitbucket®, Atlassian Crowd®, Confluence®, Jira®, Jira Service Management™, Opsgenie®, and Statuspage™ are registered trademarks of Atlassian.
Amazon Web Services™, AWS™ and the “Powered by Amazon Web Services” logo are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries.

Utoolity® is a registered trademark of Utoolity GmbH.
© 2026 Utoolity GmbH. All rights reserved.