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

Unknown macro: {spacejump}

or visit the current documentation home.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

You can use the AWS CloudFormation Stack task to create, update or delete an AWS CloudFormation stack defined by a template provided via URL or inline and specify template parameters and advanced options.

On this page:

Configuration

To ease common scenarios, the Create action allows to Update [the] stack, if it already exists, similarly the Update action allows to Create [the] stack, if it does not already exist.

To configure an AWS CloudFormation 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 AWS CloudFormation task, or click Add Task and then AWS CloudFormation Task to create a new task.
  3. Complete the following settings:

    1. 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.

      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.

    2. Actions supported by this task:

      Create

       
      Update stack, if it already existsCheck to apply the Update action, if the stack already exists. Clear to trigger a build failure otherwise.
      Stack Name

      Specify a stack name.

      Template Source

      Specify the stack template source as an S3 URL or inline in JSON format. Insert fragments from the inline Examples dialog to get started.

      Parameters(Optional) Specify parameters in JSON format. Insert fragments from the inline Examples dialog to get started.
      Advanced Options 
      Tags(Optional) Tag the stack.
      Notification ARN(Optional) Specify the Amazon SNS topic ARN stack related events should be published to.
      Creation Timeout (minutes)Specify how much time can pass before the stack creation is considered failed.
      On failure action

      Select the action that will be taken if stack creation fails.

      Stack Rollback

      Stack rollback is currently handled as follows, hopefully covering the majority of use cases (please let us know otherwise):

      • A stack rolled back successfully by CloudFormation is treated as a failed build by Bamboo.
      • A stack not rolled back due to rollback being disabled explicitly is still treated as a failed build by Bamboo.
      Enable IAM(Optional) Check if the stack should be allowed to access IAM resources.
      Stack Policy Source(Optional) Specify which update actions users can do and which resources they can take action on. See the Stack Policy Reference and Sample Stack Policies for details.

      Update

       
      Create stack, if it does not already exist

      Check to apply the Create action, if the stack does not already exists. Clear to trigger a build failure otherwise.

      Don't fail for no-op updateCheck to not fail the build, if the update does not have affect any resource. Clear to trigger a build failure otherwise.
      Stack Name or ID
      Specify the target stack. You can use its name or ID.
      Stack Template Sourcesee Create above
      Parameterssee Create above
      Advanced Options 
      Notification ARN
      see Create above
      Enable IAM
      see Create above 
      Stack Policy Sourcesee Update above
      Stack Policy During Update Source

      (Optional) Override which update actions users can do and which resources they can take action on. See the Stack Policy Reference and Sample Stack Policies for details.

      Delete

       
      Stack Name or ID

      see Update above

      Validate

      The Validate action operates on a template rather than a stack. It has been included in this task for ease of use.

      Stack Template Source

      see Create above

Frequently Asked Questions (FAQ)

  • No labels