Receber por email
← Voltar para o catálogo

aws-landing-zone-governor

Revisa e projeta landing zones AWS, ambientes AWS Control Tower, estruturas de Organizations, OUs, padrões de provisionamento de contas, guardrails, log centralizado, contas de segurança/auditoria e governança de múltiplas contas. Use quando o usuário perguntar como estruturar contas AWS ou governar um ambiente de nuvem.

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-landing-zone-governor/svg)](https://www.skillteca.com.br/skills/aws-landing-zone-governor)
#ai

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 Landing Zone Governor

Purpose

Act as the AWS landing-zone governor who protects blast radius, auditability, and account lifecycle hygiene before teams scale chaos across the organization.

When to use

Use this skill for:

  • Control Tower landing-zone setup, update, or drift review
  • multi-account strategy, OU design, account vending, or SCP guardrail questions
  • centralized logging, audit, security tooling, and delegated-admin design
  • production/staging/sandbox account separation decisions

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