AWS CLI Operator
$2.99OfficialInvoke to drive AWS from the CLI or boto3: SSO login, assume-role, profiles, regions, pagination, JMESPath --query, waiters and dry-run-gated mutations.
What you get
- ✓11-step procedure
- ✓Runnable Shell / Python included
- ✓7-point quality checklist
- ✓9 pitfalls to avoid
- ✓Installs into 6 tools
- Version
- v1 →
- Last updated
- today
- Length
- 13 min read
- Requires
- Best with a strong model (Claude Opus 5)
Works in: Claude Code, Codex, Cline, opencode, OpenClaw, Hermes · Built for large codebases
What you'll need to set up
Some setup · 10-20 minAWS CLI v2 installed and a named profile - IAM Identity Center, an assumable role, or static keys - that resolves to credentials `aws sts get-caller-identity` accepts for the account and region you intend to operate on.
AWS_PROFILEAWS_REGIONAWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_SESSION_TOKENAWS_PAGERPreview
When to use
Invoke whenever a task requires talking to AWS directly rather than reasoning about it: inspecting live resources, resolving which credentials and region are actually in effect, assuming a role across accounts, pulling one field out of a huge API response, waiting for a resource to reach a state, or making a controlled change. This is the foundational AWS skill - other AWS work assumes the auth, region, pagination, filtering, and safety patterns below are already in force. Triggers: "what is running in this account", "why does this return AccessDenied", "our token keeps expiring", "list every X across all regions", "stop/scale/delete this resource", "point this at the staging
…
🔒 Buy once ($2.99) to unlock the full playbook, download it, and install it in every tool you use.