Skip to content

Document scalable secret management with external vaults - #462

Merged
thebiglabasky merged 5 commits into
mainfrom
herve/manage-secrets-at-scale
Jul 30, 2026
Merged

Document scalable secret management with external vaults#462
thebiglabasky merged 5 commits into
mainfrom
herve/manage-secrets-at-scale

Conversation

@thebiglabasky

Copy link
Copy Markdown
Contributor

Summary

  • add a canonical guide for loading external secrets at deploy time and scoping them to Checkly groups and checks
  • add researched GitHub Actions recipes for AWS Secrets Manager, Google Secret Manager, Azure Key Vault, and HashiCorp Vault
  • clarify deployment ownership, rotation, least privilege, and the difference between deploy-time injection and runtime secret retrieval
  • correct construct examples to use secret() instead of presenting {{...}} as a deployment-time secret source

Why

Large account-level secret sets are sent to every check execution and do not scale sustainably. These guides document the supported architecture: use an external manager as the value source, authenticate CI with short-lived OIDC credentials, and deploy each secret at the narrowest Checkly scope.

Validation

  • Mintlify broken-links scan
  • frontmatter and canonical integrity checks
  • legacy redirect destination checks
  • docs.json parsing and regenerated sitemap
  • embedded TypeScript, YAML, Bash, and JSON examples
  • git diff --check

@mintlify

mintlify Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
checkly-422f444a 🟢 Ready View Preview Jul 30, 2026, 1:41 PM

@thebiglabasky
thebiglabasky marked this pull request as ready for review July 30, 2026 14:07
@thebiglabasky
thebiglabasky merged commit cd176f5 into main Jul 30, 2026
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant