aws

Manage AWS resources across multiple accounts via the CLI with credential refresh and safety confirmations.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/timi-ty/agent-forge --skill aws-timi-ty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws
Source: https://github.com/timi-ty/agent-forge/tree/main/skills/aws
Command: npx skills add https://github.com/timi-ty/agent-forge --skill aws-timi-ty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing AWS resources across multiple accounts with different authentication methods (static keys, IAM Identity Center, SAML SSO) is error-prone: credentials expire mid-operation, commands run against the wrong account, and destructive actions lack guardrails. This Skill maintains an account registry, enforces profile-prefixed commands, and adds confirmation gates for destructive and cost-incurring operations. ## Core Features & Use Cases - Multi-Account Registry: Tracks all configured AWS accounts in ~/.aws/account-registry.json with safe switching between static keys, IAM Identity Center, and saml2aws SAML SSO profiles. - Automatic Credential Refresh: Detects expired tokens (ExpiredTokenException, RequestExpired) and re-authenticates using the account's original auth method, then retries the failed command. - Safety Rails: Requires explicit confirmation before destructive operations (terminate, delete, purge) and warns about cost-incurring resources with the affected account name and ID. - Use Case: You ask to list running EC2 instances, but your SSO session expired overnight. The Skill detects the failure, runs aws sso login, verifies identity with sts get-caller-identity, and retries the query against the correct account. ## Quick Start Ask the agent to list all running EC2 instances in your active AWS account and show them in a table.

Frequently Asked Questions about aws

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage multiple AWS accounts from the CLI?

Maintain an account registry at ~/.aws/account-registry.json that maps friendly names to AWS profiles, regions, and auth methods. Prefix every command with AWS_PROFILE=<profile> and verify the active account with aws sts get-caller-identity before operating.

How do I switch between AWS accounts with different auth methods?

Test the target account's credentials with sts get-caller-identity, refresh them if expired using its auth method (sso login, saml2aws login, or aws configure), then update the active field in the registry. Confirm the switch by re-running get-caller-identity.

Why does my AWS CLI command fail with ExpiredTokenException?

ExpiredTokenException means your temporary credentials from SSO or SAML have expired. Re-authenticate using the original method, such as aws sso login --use-device-code or saml2aws login, verify with sts get-caller-identity, then retry the failed command.

Can I use SAML SSO with MFA for AWS CLI access?

Yes, use saml2aws with the Browser provider, which opens a Chromium window for login and MFA completion. Programmatic providers like KeyCloak or Okta cannot handle MFA flows, so the Browser provider is required.

How do I prevent accidentally deleting AWS resources in the wrong account?

Always display the active account name and ID before destructive operations like terminate-instances or delete-stack, and require explicit user confirmation. Warn the user when the request seems to target a different account than the active one.