AWS CodeBuild

Spinnaker supports AWS CodeBuild as a continuous integration system.

Setting up AWS CodeBuild as a Continuous Integration (CI) system within Spinnaker allows you to:

  • trigger pipelines when an AWS CodeBuild build changes its phase or state
  • add an AWS CodeBuild stage to your pipeline

The AWS Codebuild stage requires Spinnaker 1.19 or later.


AWS CodeBuild project

You need to have an AWS CodeBuild project. To create a project, follow the instructions on how to create a CodeBuild service role (AWS CLI) .

Next, run the following command (make sure you replace the service role with the one created and region of your own choice):

aws codebuild create-project \
  --name spinnaker-project \
  --source "type=GITHUB,location=" \
  --artifacts "type=NO_ARTIFACTS" \
  --environment "type=LINUX_CONTAINER,computeType=BUILD_GENERAL1_SMALL,image=aws/codebuild/standard:4.0" \
  --service-role <YOUR_SERVICE_ROLE> \
  --region <YOUR_AWS_REGION>

Note: The project created by the command above doesn’t produce artifacts since NO_ARTIFACTS is specified for artifacts type. To create a project that generates artifacts, follow the instructions in the AWS CodeBuild user guide .

For more information about how to create a project to meet your needs, see the use case based samples in the AWS CodeBuild documentation.

IAM Role

You need to have an IAM role that has the following permissions:

  "Version": "2012-10-17",
  "Statement": [
      "Effect": "Allow",
      "Action": [
      "Resource": "*"

This role has to trust the Spinnaker auth role so that the managing account can assume this role to call CodeBuild. You can edit your trust relationship to add the following policy:

  "Version": "2012-10-17",
  "Statement": [
      "Effect": "Allow",
      "Principal": {
        "AWS": <Your Spinnaker Auth Role>
      "Action": "sts:AssumeRole"

Configure Spinnaker to work with AWS CodeBuild

Use the following Halyard commands to create an AWS CodeBuild account, enable the AWS CodeBuild integration, and re-deploy Spinnaker:

hal config ci codebuild account add $ACCOUNT_NAME \
  --account-id $ACCOUNT_ID \
  --assume-role $ASSUME_ROLE \
  --region $REGION

hal config ci codebuild enable

hal deploy apply

Configure an AWS CodeBuild stage

To run an AWS CodeBuild build as part of a Spinnaker pipeline, perform the following steps:

  1. Create a stage of type AWS CodeBuild.

  2. Configure the stage by selecting the following:

    • AWS CodeBuild account to use to run the build
    • The project name from the dropdown list
  3. (Optional) In the Source Configuration section, you can also do the following:

  • Select the source artifact to use as the build source. If not specified, the source configured in the project is used.
  • Specify the source version . of the build source. If not specified, the latest version is used.
  • Specify the buildspec file . If left blank, the buildspec configured in the project is used.
  • Select secondary build sources. If not specified, the secondary sources configured in the project is used.
  1. (Optional) In the Environment Configuration section, you can specify the image tag or image digest that identifies the Docker image to use. If not specified, the image configured in the project is used. Note: As a prerequisite, follow this user guide to set up your registry credentials in the project configuration.

  2. (Optional) In the Advanced Configuration section, you can specify environment variables to use in the build. Only environment variables in plain text are supported. Parameter Store / Secrets Manager environment variables can be configured in the project.

  3. (Optional) In the Produces Artifacts section, you can supply any artifacts that you expect the build to create in order to make these artifacts available to downstream stages. AWS CodeBuild supports creating S3 artifacts in ZIP format, which will be converted to Spinnaker artifacts and injected into the pipeline on completion of the build.

While your build is running, the stage details provide the following information:

  • Current status of the build
  • ARN of the build
  • The link to view the build in the AWS CodeBuild Console
  • The link to view the build logs in AWS CloudWatch Logs
  • The link to view the build logs in S3

Configure your pipeline trigger (Optional)

Configure your pipeline to get triggered when an AWS CodeBuild build completes:

  1. Follow these instructions to set up a notification rule for your project. To trigger the pipeline on completion of the build, select Succeeded and Failed in the Events that trigger notifications section under Build state.

  2. Follow these instructions to create an Amazon Pub/Sub trigger. Keep the following guidelines in mind:

  • Skip the step to create SNS topic, as we will use the SNS topic created in step 1.
  • Create an SQS queue and subscribe the queue to the SNS topic.
  • Skip the step to create an S3 bucket, as the notification will be sent from CodeBuild instead of from S3.
  • Write the Echo configuration and set up the Amazon Pub/Sub trigger in the Spinnaker UI.
  1. Start a build in CodeBuild. Your pipeline gets triggered when the build completes.
Last modified May 4, 2021: rest of migration (700781a)