_CloudFormationNote
Some of the resource types supported by Dedicated Tasks can alternatively be provisioned as a AWS CloudFormation Resource Type by means of the CloudFormation Stack task, for example:
- AWS::ElasticBeanstalk:: Application / ApplicationVersion / Environment
- AWS::ECS:: Cluster / Service / TaskDefinition
- AWS::CloudFormation:: Stack
Choosing between CloudFormation stacks vs. dedicated tasks
Both approaches have specific use cases and pros/cons, for example:
- Some resource actions do not have dedicated CloudFormation support (though can be implemented as Custom Resources meanwhile).
- Some resources do not have dedicated task support (though can be provisioned via the AWS Credentials Variables task and the AWS CLI meanwhile).
- CloudFormation stacks allow you to manage your infrastructure as code, at the expense of a steeper learning curve and everyday usability
- Dedicated tasks are easier to get started with and maintained via Bamboo's user interface
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.
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.
© 2024 Utoolity GmbH. All rights reserved.