AWS Ecosystem
AWS is the broad cloud route when work involves AWS account resources, Bedrock/AgentCore, CDK/CloudFormation, serverless, containers, storage, IAM, or AWS-supported agent tooling. Source: Ecosystem Capability Coverage, 2026-06-27; Skill Resolver, 2026-06-27
When To Use This
Use AWS when the infrastructure, account, deployment, or cloud service is AWS-specific. Use AWS Agent Toolkit for service selection, docs, agent-aware guidance, and AWS MCP/server paths. Use aws CLI when the exact account/API operation is known. Source: AWS Agent Toolkit, 2026-06-27; Skill Resolver, 2026-06-27
Decision Matrix
| Need | Route | Verification |
|---|---|---|
| Agent-aware AWS guidance | AWS Agent Toolkit | Source/tool output |
| Account-specific reads | aws CLI |
aws sts get-caller-identity and read result |
| Local AWS-shaped tests | Floci or emulator | Local test result |
| Infrastructure mutation | CLI/IaC with plan/read-first | Dry-run, plan, or readback |
Core Model
AWS is too broad to route through one skill. Split tasks into account state, architecture guidance, local emulation, and mutation safety. The account/region/environment check is non-negotiable before writes. Source: Skill Resolver, 2026-06-27
Routing Summary
Preferred order: AWS Agent Toolkit for AWS-supported agent guidance, aws CLI for real account reads/writes, Floci or local emulators for integration tests, and service CLI registry for generic cloud safety. Source: Skill Resolver, 2026-06-27; config/capability-harvest-seeds.json
Failure Modes
- Running against the wrong AWS profile or region.
- Letting agent docs choose architecture without account constraints.
- Mutating production without dry-run, plan, or readback.
- Using real cloud where local emulation would prove the same behavior.
Verification Path
Run aws sts get-caller-identity and confirm region/profile before reads or writes. For IaC, use plan/preview. For local emulation, show the emulator/test result and state any service-parity gap. Source: config/capability-harvest-seeds.json; Skill Resolver, 2026-06-27
Timeline
- 2026-06-27 | Canonical ecosystem page created so AWS has a platform-level route alongside AWS Agent Toolkit and Floci. Source: User request, 2026-06-27; Ecosystem Capability Coverage