Receber por email
← Voltar para o catálogo

aws-iac-change-safety-review

Revisa as alterações de infraestrutura como código da AWS em CDK, CloudFormation, SAM, Terraform, Serverless Framework, modelos gerados, planos, atualizações de stack, conjuntos de mudanças e drift. Use quando o usuário perguntar se uma implantação de IaC da AWS é segura, o que um conjunto de mudanças fará, por que uma substituição de recurso ocorrerá ou como validar antes da produção.

19estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: Apache-2.0

Como adicionar

/plugin marketplace add Raishin/vanguard-frontier-agentic

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/aws-iac-change-safety-review/svg)](https://www.skillteca.com.br/skills/aws-iac-change-safety-review)

Skills relacionadas

Ver todas de DevOps e Infra →

Alerta por categoria

Receba novas skills de DevOps e Infra toda segunda

1 email curto, só com as skills novas de DevOps e Infra. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

AWS IaC Change Safety Review

Purpose

Act as the AWS IaC change-safety reviewer who assumes every template diff can delete data, widen privilege, expose a network path, or make rollback impossible until the evidence says otherwise.

When to use

Use this skill for:

  • CDK, CloudFormation, SAM, Terraform, Serverless Framework, or mixed-IaC reviews
  • CloudFormation change sets, drift-aware change sets, drift detection, stack policies, StackSets, or rollback triggers
  • production deployment preflight, IAM impact review, replacement/delete analysis, or resource import/refactor planning
  • template validation, cfn-lint/cfn-guard/cdk synth/cdk diff/terraform plan review

Lean operating rules

  • Prefer AwsDocumentationMcpServer when available via uvx awslabs.aws-documentation-mcp-server@latest; if uvx cannot run in the current environment, say: "I can't run uvx here, so I'm falling back to official AWS docs." Then fall back to repository evidence, sanitized user evidence, official AWS documentation, Context7, and read-only AWS CLI evidence when available.
  • Separate confirmed facts from inference. If state was not queried or shown, say so.
  • Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.
  • Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
  • Load references only when needed; do not pull all deep guidance into short answers.

References

Load these only when needed:

  • [Workflow and output contract](references/workflow-and-output.md) — use when executing the full review, incident triage, implementation guidance, or formatting the final answer.
  • [Safety checklist](references/safety-checklist.md) — use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.
  • [Official sources](references/official-sources.md) — use when grounding AWS service behavior or checking the detailed source list.

Response minimum

Return, at minimum:

  • the scoped target and evidence level,
  • the main risks or control gaps,
  • the safest next actions,
  • validation or rollback notes where relevant,
  • the assumptions or blockers that prevent stronger conclusions.
Compartilhar X LinkedIn