AWS CodeCommit
Jasper code reviews on CodeCommit pull requests.
What it does
- Reviews. When a pull request is created or gets new commits in a repository with reviews on, Jasper reviews it.
- Comments. Findings are posted as comments on their lines, and the summary as a comment on the pull request. Jasper does not approve, merge or push.
- Reviews page. CodeCommit reviews appear on the Reviews page next to GitHub ones, labelled AWS CodeCommit.
Before you start
- You need to be an owner or admin of your Jasper organisation. AWS CodeCommit is off until an admin turns it on in Settings → Features.
- You need permission in your AWS account to create an IAM role, an SNS topic and an EventBridge rule.
1. Create the IAM role
Open Settings → AWS CodeCommit. Jasper shows a trust policy and a permission policy. Create an IAM role with both. The trust policy lets only Jasper assume the role, and only with the external id shown for your organisation, so no AWS access key is ever shared. The permission policy allows listing repositories, reading pull requests, differences and files, and posting comments.
2. Create the topic and rule
- Create an SNS topic in the repositories' region.
- Create an EventBridge rule on the default event bus for CodeCommit pull request state changes (the pattern is shown on the page), with the topic as its target. Let
events.amazonaws.compublish to the topic in its access policy.
3. Connect, subscribe and choose repositories
- Enter the role ARN, region and topic ARN. Jasper assumes the role to check it works before it saves them.
- Subscribe the HTTPS endpoint shown on the page to the topic. Jasper confirms the subscription itself, and only for the topic you entered. Subscribe after connecting: before that, Jasper refuses the confirmation.
- Click Load repositories, then Reviews off, turn on next to the repositories Jasper should review.
Jasper checks the signature of every message and that it came from your topic, account and region. Anything else is refused.
Your data and disconnecting
- Jasper keeps the role ARN, region, topic and the external id (encrypted). It holds the role's temporary credentials only while it works on a review.
- Disconnect makes Jasper forget the role and topic. Delete the role, rule and topic in your AWS account to remove them there.
- Jasper keeps each delivery it receives, including refused ones, in its webhook log.
New to Jasper? try it free.