Skip to content

Event Source for AWS CodeCommit

This event source captures notifications from an AWS CodeCommit repository whenever a specific action, such as a new commit or the creation of a pull request, happens in this repository.


  • CodeCommit Repository and Branch
  • Amazon Resource Name (ARN)
  • API Credentials

CodeCommit Repository and Branch

If you don't already have an AWS CodeCommit repository, create one by following the instructions at Create an AWS CodeCommit repository. The repository should contain at least one branch. To create one, follow the instructions at Create a branch in AWS CodeCommit.

CodeCommit repository

Amazon Resource Name (ARN)

A fully qualified ARN is required to uniquely identify the AWS CodeCommit repository.

The easiest way to obtain the ARN of a CodeCommit repository is by using the AWS CLI. The following command retrieves the information of a repository called triggermeshtest in the us-west-2 region:

$ aws codecommit get-repository --repository-name triggermeshtest --region us-west-2
    "repositoryMetadata": {
        "accountId": "123456789012",
        "repositoryId": "510acd3d-b96d-473c-bbe4-a8c6799d02a9",
        "repositoryName": "triggermeshtest",
        "defaultBranch": "main",
        "lastModifiedDate": "2020-07-20T20:54:27.806000+02:00",
        "creationDate": "2020-07-20T20:49:12.324000+02:00",
        "cloneUrlHttp": "",
        "cloneUrlSsh": "ssh://",
        "Arn": "arn:aws:codecommit:eu-central-1:123456789012:triggermeshtest"

If you don't have the AWS CLI installed on your workstation, you can use the template below to compose a fully qualified ARN of a CodeCommit repository.


API Credentials

The TriggerMesh event source for Amazon CodeCommit authenticates calls to the AWS API using AWS Access Keys. The page Understanding and getting your AWS credentials contains instructions to create access keys when signed-in either as the root user or as an IAM user. Take note of the Access Key ID and Secret Access Key, they will be used to create an instance of the event source.

It is considered a good practice to create dedicated users with restricted privileges in order to programmatically access AWS services. Permissions can be added or revoked granularly for a given IAM user by attaching IAM Policies to it.

As an example, the following policy contains only the permissions required by the TriggerMesh AWS CodeCommit event source to operate:

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

Creating an IAM user

Deploying an Instance of the Source

Open the Bridge creation screen and add a source of type AWS CodeCommit.

Adding an AWS CodeCommit source

In the Source creation form, give a name to the event source and add the following information:

  • AWS ARN: ARN of the CodeCommit repository, as described in the previous sections.
  • Branch name: Name of the Git branch the source should be watching for commits.
  • Event types: List of event types the event source should subscribe to.
  • AWS Secret: Reference to a TriggerMesh secret containing an Access Key ID and a Secret Access Key to communicate with the AWS CodeCommit API, as described in the previous sections.

AWS CodeCommit source form

After clicking the Save button, you will be taken back to the Bridge editor. Proceed to adding the remaining components to the Bridge, then submit it.

Bridge overview

A ready status on the main Bridges page indicates that the event source is ready to receive notifications from the AWS CodeCommit repository.

Bridge status

Event Types

The AWS CodeCommit event source emits events of the following types: