Business-aware severity
Every finding is paired with your revenue tags, customer tiers, and regional exposure. The CLI sorts by dollars at risk — not by "high / medium / low." Critical means the order pipeline. Low means a dev sandbox.
BlueArch CLI pairs the world's largest AWS misconfiguration database with your business context — revenue tags, customer tiers, regional exposure — so the first alert you see is the one that actually matters. Notes, runbooks, and AI triage, one terminal away.
Three things every SRE and solution architect asks for, finally in one tool.
Every finding is paired with your revenue tags, customer tiers, and regional exposure. The CLI sorts by dollars at risk — not by "high / medium / low." Critical means the order pipeline. Low means a dev sandbox.
Per-finding notes that travel with the engineer, not the resource. Snooze with reason, escalate to JIRA, or ask InfraGPT to draft the remediation PR. State is shared across your team, not stuck in someone's terminal history.
Every finding ships with a tested remediation — Terraform, CDK, or raw AWS CLI. Apply it as a dry-run, review the diff, and ship. No SaaS in the loop; the CLI runs in your VPC and writes to your account.
We went from triaging Security Hub findings on Mondays to a 9am Slack digest with three things to fix. BlueArch knows which of our buckets actually serve customer traffic — Security Hub never did.
brew list --formula bluearch-aws-core >/dev/null 2>&1 || brew install bluearchio/tap/bluearch-aws-corebrew install bluearchio/tap/bluearch-aws-opsbrew list --formula bluearch-aws-core >/dev/null 2>&1 || brew install bluearchio/tap/bluearch-aws-coreTypical: 1–3 minThis check does nothing when the Homebrew Core formula is already installed. Otherwise, the fully qualified install trusts only bluearch-aws-core.
brew install bluearchio/tap/bluearch-aws-opsTypical: 1–3 minInstalls the signed bluearch-aws-ops binary and trusts only that formula, not the whole tap.
aws sso login --profile my-profileexport AWS_PROFILE=my-profileTypical: 1–2 minKeep using your existing AWS SSO profile. Ops starts read-only and does not deploy infrastructure for a local scan.
bluearch-aws-core start --daemonbluearch-aws-core statusTypical: under 30 secCore starts its API on 127.0.0.1:8094 and the installed Ops dashboard on http://127.0.0.1:8095.
Use Resources to start a read-only inventory scan, then inspect resources and scan history without returning to the terminal.
The release installer verifies the GitHub assets and installs Core automatically when it is missing. Add the install directory to PATH for this shell.
curl -fsSL https://github.com/bluearchio/bluearch-aws-ops/releases/latest/download/install-linux.sh | bashexport PATH="$HOME/.local/bin:$PATH"Trust only Core and Ops, then retry. Whole-tap trust and HOMEBREW_NO_REQUIRE_TAP_TRUST are not required.
brew trust --formula bluearchio/tap/bluearch-aws-corebrew trust --formula bluearchio/tap/bluearch-aws-opsbrew install bluearchio/tap/bluearch-aws-opsFor deep technical details, see the docs. Or ask InfraGPT.
Install in five minutes. Get your first business-aware report on coffee #2.