Info |
---|
Requirements Tasks for AWS supports adding and deploying OpsWorks Apps with dedicated tasks. All other components are considered long running and expected to be either provisioned manually or via AWS CloudFormation (see Alternative workflow via CloudFormation below). |
Workflow
The stack architecture is illustrated by the diagram in What is AWS OpsWorks?:
The resulting deployment workflow comprises the following activities:
provision an application server stack, either manually via the AWS Management Console or via AWS CloudFormation (see Alternative workflow via CloudFormation below)
(optional) upload the application source code (the 'App Source') – see the Upload File(s) action of the Amazon S3 Object task
OpsWorks also supports other repository types besides S3, such as Git, SVN or HTTPcreate an app – see the Create App action of the AWS OpsWorks App task
deploy the app – see the Deploy App action of the AWS OpsWorks Deployment task
Alternative workflow via CloudFormation
As an alternative to using the AWS OpsWorks tasks built into Tasks for AWS, it is also possible to provision the OpsWorks components directly via the AWS CloudFormation Stack task and the corresponding CloudFormation resource types:
A typical workflow based on CloudFormation might look as follows:
(optional) upload the application source code (the 'App Source') – see the Upload File(s) action of the Amazon S3 Object task
OpsWorks also supports other repository types besides S3, such as Git, SVN or HTTPcreate/update the CloudFormation stack that provisions the OpsWorks app, instance(s), layer and environment – see the Create Stack action of the AWS CloudFormation Stack task
You can use the Update stack, if it already exists option to reuse the same Bamboo job for both actionsdeploy the app – see the Deploy App action of the AWS OpsWorks Deployment task
Frequently Asked Questions (FAQ)
Include Page | ||||
---|---|---|---|---|
|
Questionslist macro | ||||||||
---|---|---|---|---|---|---|---|---|
|