AWS CodePipeline status in your Mac menu bar

What you see for each pipeline

• Every stage as a row of dots: green when it succeeded, amber while it runs, red when it failed.
• Expand a pipeline to see each action’s status, when it last ran, and the AWS error code and message when it fails.
• An Open in browser link on each action that jumps to that action’s execution details.
• The commit message that started the run, when the source action reports one.
• Pipelines grouped by profile · region, so staging and production accounts stay apart.

Set it up

1. Make sure the profile works in your terminal: aws sso login --profile work for IAM Identity Center (SSO), or aws configure --profile personal for an access key.
2. In ShipBoard, click + and choose AWS.
3. Pick the profile and region, then tick the pipelines you want on the board.
4. When an SSO session expires, the group shows Log in to AWS, which runs aws sso login for that profile.

What access ShipBoard needs

ShipBoard only reads. It can’t start, stop, retry or approve anything. If you’d rather not attach a managed policy, this is the whole policy it needs:

{
  "Version": "2012-10-17",
  "Statement": [{
    "Effect": "Allow",
    "Action": [
      "codepipeline:ListPipelines",
      "codepipeline:GetPipeline",
      "codepipeline:GetPipelineState"
    ],
    "Resource": "*"
  }]
}

Good to know

• Checks every 30 seconds by default (15 seconds to 5 minutes), and every 15 seconds while AWS can’t be reached.
• Works with any profile the AWS CLI can use, including SSO. ShipBoard doesn’t assume roles beyond what the profile itself defines.
• The region list covers 20 common regions, plus your profile’s default region.
• The pipeline picker shows the first page of ListPipelines results, so very large accounts may not see every pipeline listed.

AWS CodePipeline FAQ