AWS CodePipeline Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
* The example requires a GitHub repository to be available. We'll use https://github.com/ovidiuf/aws-pipeline-source-example. | * The example requires a GitHub repository to be available. We'll use https://github.com/ovidiuf/aws-pipeline-source-example. | ||
* The CodeBuild and CodePipeline service roles must be created in advanced and referred from the CloudFormation stack specification by their ARN. I tried creating them as part of the same stack, but I got: "CodeBuild is not authorized to perform: sts:AssumeRole on ...". If they exist when the stack creation is attempted, it works. | * The CodeBuild and CodePipeline service roles must be created in advanced and referred from the CloudFormation stack specification by their ARN. I tried creating them as part of the same stack, but I got: "CodeBuild is not authorized to perform: sts:AssumeRole on ...". If they exist when the stack creation is attempted, it works. <Font color=darkgray>TODO: try to declare them in the same stack, experiment with dependencies, try to make this work.</font> | ||
==Procedure== | ==Procedure== | ||
Revision as of 05:45, 15 March 2019
External
Internal
Overview
Simple GitHub - Simulated Shell Build - Simulated Deployment Pipeline
Prerequisites
- The example requires a GitHub repository to be available. We'll use https://github.com/ovidiuf/aws-pipeline-source-example.
- The CodeBuild and CodePipeline service roles must be created in advanced and referred from the CloudFormation stack specification by their ARN. I tried creating them as part of the same stack, but I got: "CodeBuild is not authorized to perform: sts:AssumeRole on ...". If they exist when the stack creation is attempted, it works. TODO: try to declare them in the same stack, experiment with dependencies, try to make this work.
Procedure
The CodePipeline pipeline, the delegate CodeBuild project, required service roles and the S3 bucket to keep the artifacts produced by the pipeline will be created as part of one CodeFormation stack: