Skip to main content
Complete every item below before running the installer. The preflight script at the bottom can verify them all in one shot.

Required tools

Install these CLI tools on the machine you will deploy from.
Run node -v && aws --version && sam --version to quickly confirm all three are installed.

AWS account requirements

Amazon Bedrock enabled in at least one supported region. See Bedrock Regions for the full list.
Model access granted for Claude Sonnet (anthropic.claude-sonnet-4-20250514). Open the Bedrock Model Access console and request access if the status is not Access granted.
IAM user or role with deploy permissions. The deploying principal needs at minimum:
  • cloudformation:*
  • lambda:*
  • apigateway:*
  • iam:CreateRole, iam:AttachRolePolicy, iam:PassRole
  • s3:CreateBucket, s3:PutObject
  • bedrock:InvokeModel
Or attach the AWS-managed AdministratorAccess policy for a zero-friction first deploy.
Never use root-account credentials. Create a dedicated IAM user or assume a role instead.

GitHub requirements

Requirements depend on the install type.

Organization install

You are an Owner or Admin of the GitHub organization where you want to install MergeWatch.

Personal install

You are signed in to the personal GitHub account where you want to install MergeWatch. No special role is needed.
Not sure which install type to pick? Organization installs cover every repo in the org. Personal installs cover repos owned by your user account. You can always add the other later.

Check everything at once

Run the built-in preflight check instead of verifying each prerequisite manually:
npx mergewatch@latest check
The command validates:
  • Node.js, AWS CLI, and SAM CLI versions
  • AWS credentials and Bedrock model access
  • GitHub authentication and permissions
Each check reports pass or fail. Failed checks include a direct link to the relevant fix instructions above.
Run npx mergewatch@latest check one more time right before you start the install to make sure nothing has changed.