Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From grc-portfolio
Deploy AWS CloudFormation stacks for S3, CloudFront, Route 53, ACM, and optionally the contact form Lambda + API Gateway.
How this command is triggered — by the user, by Claude, or both
Slash command
/grc-portfolio:infraThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Deploy Infrastructure Provisions all AWS infrastructure needed to host your GRC portfolio using CloudFormation: - **S3 bucket** — stores your built website files - **CloudFront distribution** — global CDN with HTTPS - **Route 53** + **ACM certificate** — custom domain with SSL *(if configured)* - **Lambda + API Gateway** — contact form backend *(if configured)* Deployment takes ~5–15 minutes. Stack outputs (bucket name, distribution ID, CloudFront URL) are automatically saved back to `site-config.json`. ## Arguments - `$1` — Project directory containing `site-config.json` (optional; ...
Provisions all AWS infrastructure needed to host your GRC portfolio using CloudFormation:
Deployment takes ~5–15 minutes. Stack outputs (bucket name, distribution ID, CloudFront URL) are automatically saved back to site-config.json.
$1 — Project directory containing site-config.json (optional; defaults to current directory)Run /grc-portfolio:preflight first. All checks must pass.
/grc-portfolio:infra ~/Desktop/repos/my-grc-portfolio
/grc-portfolio:infra
Run /grc-portfolio:deploy to build and push your site to the new infrastructure.
npx claudepluginhub vantainc/claude-grc-engineering --plugin grc-portfolio2plugins reuse this command
First indexed Jul 18, 2026
/infraAudits a pull request for infrastructure and deployment safety risks, including downtime, database container restarts, and config equivalence.
/infraDesigns Infrastructure as Code configurations using Terraform, CDK, or CloudFormation based on a natural language requirement. Specify optional tool preference.
/infraAdds and validates one production infrastructure bundle (Health, Security, Backup, or Deploy) at a time for the detected stack, with full verification.
/infraValidates, plans, and deploys Infrastructure as Code using Terraform, CloudFormation, Pulumi, or CDK with policy enforcement, cost estimation, drift detection, and test execution.
/infraManages infrastructure: creates modular Harness repos with CI/CD pipelines, Helm charts, Terraform modules; tracks Jira deployments, views pipeline status. Supports create-repo, deploy, pipeline, status.
/infraGenerates production-ready Terraform IaC for AWS, Azure, or GCP with multi-env setups, modules (network/compute/database/etc.), scripts, and policies.