Configure an AWS CodeBuild Pipeline

EdgeBit gives developers context about new and modified software dependencies when submitted a pull request or pushing a new commit before it merges into main.

This context is useful for:

• vulnerabilities: understand vulnerabilities present in the selected version(s)
• recommendations: see a recommended version with fixed vulnerabilities, if available
• standardization: gain context about versions of the same dependnecy that other teams may be using at your organization – think of this as a gentle nudge to standarize via social proof

This document will walk through setting up an AWS CodeBuild project.

The action uses the Syft open source project to generate the software bill of materials (SBOM).

Create your CodeBuild Project

Follow the prompts to create a new project if you don’t have an existing one. Ensure that the Privileged option is checked under the Environment settings. This is required to build container images in your project.

Create BuildConfig File

In your GitHub repo, create or edit your buildspec.yml:

This example is a minimal example of a container build. For an existing project, mix these commands in where it makes sense. Here’s what it does:

1. Installs ebctl and Syft
2. Generates a software bill of materials (SBOM) from the current directory, detecting most common programming languages
3. Uses your EdgeBit Access Token to upload the SBOM to EdgeBit and ties it to a component

version: 0.2

env:
  shell: bash
  variables:
    IMAGE_TAG: '1.2.3'
    IMAGE: 'registry.example.com/projectname'
    NAME: 'projectname'
    EDGEBIT_URL: 'https://example.edgebit.io'
    GH_REPO: 'https://github.com/example/projectname'
  secrets-manager:
    EDGEBIT_API_KEY: example.edgebit.io/EdgeBitAPIKey

phases:
  install:
    commands:
      # Install ebctl
      - curl -sSfL https://install.edgebit.io/releases/edgebit-cli/latest/edgebit-cli_Linux_$(uname -m | sed 's/aarch64/arm64/').tar.gz | tar xz
      # Install syft v0.74.1
      - curl -sSfL https://raw.githubusercontent.com/anchore/syft/main/install.sh | sh -s -- -b . v0.74.1
  pre_build:
    commands:
      - LATEST_SHA=$(git rev-parse HEAD)
      - FULL_IMAGE="$IMAGE:$IMAGE_TAG"
  build:
    commands:
      - docker build -t $FULL_IMAGE .
      # Generate SBOM
      - ./syft packages $FULL_IMAGE -o syft > $NAME.syft
      # Upload SBOM to component
      - |
        ./ebctl upload-sbom \
          --component $NAME \
          --tag latest \
          --tag $IMAGE_TAG \
          --repo $GH_REPO \
          --commit $LATEST_SHA \
          --image-tag $FULL_IMAGE \
          $NAME.syft        

Customize Project Inputs

Fill in the required inputs at the top of the file under env:

For simplicity this example is hardcoded to append the latest tag for SBOM in addition to the tag from the container. This indicates the newest build in the EdgeBit UI. More advanced logic can be substituted and used in the ebctl upload-sbom command.

Configure AWS Secret Manager

In the EdgeBit Console, generate a new Access Token for this project to use. You can find this in the left hand navigation under “Access Tokens”.

Save the new EdgeBit Access Token in the AWS Secret Manager as a plaintext value (not key/value). This value is referenced at the top of our buildspec.yml, so please update it with the name. Note the ARN, since we’ll use that in the IAM policy.

If you would like to comment on PRs, do the same for a Github Personal Access Token.

Configure IAM Policy

Next, add an IAM policy to the automatically generated Role used by this CodeBuid project. To do this manually, navigate to the IAM section and search for “codebuild” in the Role list. It should be something like codebuild-<projectname>-service-role.

Here’s an example role that should contain your secret’s ARN. If your organization uses automation to manage your AWS infrastructure, please follow those best practices.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "secretsmanager:GetResourcePolicy",
                "secretsmanager:GetSecretValue",
                "secretsmanager:DescribeSecret",
                "secretsmanager:ListSecretVersionIds"
            ],
            "Resource": "arn:aws:secretsmanager:us-east-1:11223344556677:secret:xxxxxxx"
        }
    ]
}

Set Up the GitHub app

Optionally, use the EdgeBit’s GitHub app to allow Developers to see a new EdgeBit check on their PRs:

1. Comments on the PR if new dependency changes are detected, highlighting:
   • New vulnerabilities and supply chain risks introduced by the changes
   • Confirming addition, modification or removal of dependency changes without issues
2. Link to more detail within EdgeBit about the current state of all known vulnerabilities

If a PR makes dependency changes and new issues are found, EdgeBit will comment with more information:

To set up the GitHub app, an admin should do the following:

1. In the EdgeBit Console, click on “Integrations” in the left navigation pane.
2. Click “New Integration” to start the GitHub app installation process.
3. Grant EdgeBit access to all repos in an organization or a subset.
4. Choose which project(s) the GitHub integration should be used with.

Test the Integration

Click “Start Build” to run your first build off the latest code. Be sure the repository contains your customized buildspec.yml.

View your Build Artifacts in the EdgeBit Console

Your EdgeBit Console contains reports about each SBOM uploaded and the current state of all vulnerabilities in your software Components.

Next: Install Machine Agent