---
name: "vanguard-aws"
displayName: "Vanguard Frontier — AWS"
description: "Curated AWS agents for IAM, EKS, Lambda, RDS, S3, and Bedrock with live-mutation guards. Routes via aws-maestro to specialist or live-guard agents based on task scope. Mutations on real AWS environments require account-ID, region, and approval confirmation before execution."
keywords: ["aws", "iam", "eks", "lambda", "rds", "s3", "bedrock", "live-guard"]
author: "Raishin"
---
# Vanguard Frontier — AWS

Curated AWS agents for IAM, EKS, Lambda, RDS, S3, and Bedrock with live-mutation guards. Routes via aws-maestro to specialist or live-guard agents based on task scope. Mutations on real AWS environments require account-ID, region, and approval confirmation before execution.

## When to engage this Power

Activate when the task references AWS services, resources, or operations. Do not activate on unrelated requests — narrow keyword matching is required to avoid false activations (Kiro Powers convention).

## Routing pattern

- **`aws-maestro-agent`** — classifies and routes the task to the right specialist

Use the maestro as the entry point: classify the task, then dispatch to one specialist or a parallel team of specialists. Never have the maestro itself execute a live mutation.

## Live-guard agents (gate_mode only)

- `aws-live-deployment-guarded-operator-agent` — never auto-dispatched; gate_mode only
- `aws-live-ecs-rollout-guard-agent` — never auto-dispatched; gate_mode only
- `aws-live-iac-change-guard-agent` — never auto-dispatched; gate_mode only
- `aws-live-pipeline-approval-operator-agent` — never auto-dispatched; gate_mode only
- `aws-live-serverless-release-guard-agent` — never auto-dispatched; gate_mode only

Live-guard agents enforce approval, target confirmation, evidence capture, and rollback plans before executing a mutation. They are never auto-dispatched — the maestro must place them in `live-guard-gate` or `runtime-evidence-gate` mode.

## Invariants

- Confirm AWS account ID and region before any live mutation.
- Live-guard agents (aws-live-*) must never be auto-dispatched; require explicit approval and rollback plan.
- IAM least-privilege review applies to every policy attachment, role assumption, and trust relationship.
- Cross-account access via assume-role must be reviewed by aws-iam-review-agent before activation.

## Where the agents live

Agent specs and adapters are part of the [Vanguard Frontier Agentic](https://github.com/Raishin/vanguard-frontier-agentic) marketplace. For this provider, see `agents/aws/` in that repository. All 47 agents in this provider ship a Kiro adapter (`harnesses/kiro-ide.agent.md`, `kiro-cli.agent.json`).

## Companion install paths

- **Claude Code:** `/plugin marketplace add Raishin/vanguard-frontier-agentic` then `/plugin install vanguard-frontier-agentic@vanguard-frontier-agentic`
- **Codex / Copilot / Cursor / Gemini CLI / Kiro (file export):** `npx vfa-export-agents --platform <harness> --provider aws --repo .`
