agentleFS
Sign inStart free
sonorateksonoratek/legiox/skills/aws-console-cli-agent/SKILL.md

aws-console-cli-agent

Skill0 starsChanged 44 days agoMITView on GitHub

configuring AWS CLI v2 profiles, SSO, or named credentials for automation

The file

Create a free account to mount
Files
SKILL.md

AWS Console CLI Agent

Summary

AWS Console automation = AWS CLI v2 + SigV4 APIs, not gcloud: install only official AWS CLI v2 bundled packages; authenticate via IAM Identity Center SSO profiles or AssumeRole temporary creds (never root, avoid long-lived IAM user keys); Organizations OUs + SCPs for multi-account; Budgets with IAM/SCP budget actions for credit burn brakes; Free Tier (post-2025) grants up to $200 credits with Free vs Paid plan semantics — Free plan auto-closes when credits expire; always tag CostCenter/Environment/Owner; prefer CloudFormation/CDK over clickops; Service Quotas before scale; Route53/EKS/ECR/EC2 ops stay AWS-namespaced so selectors do not confuse with GCP Resource Manager or Hetzner/PR-ops paths.

Instructions

  1. Pattern: aws configure sso + aws sso login --profile NAME -> Identity Center session for console-equivalent CLI without long-lived keys
  2. Pattern: aws sts assume-role --role-arn ARN --role-session-name automation -> temporary AccessKeyId/SecretAccessKey/SessionToken for scripts
  3. Pattern: aws organizations create-account + move-account into OU -> multi-account isolation before enabling expensive services
  4. Pattern: aws budgets create-budget + create-budget-action (IAM/SCP Deny) at 80/90% -> automatic spend brake before credits deplete
  5. Pattern: aws ce get-cost-and-usage + GetFreeTierUsage -> daily credit/usage reality check before provisioning
  6. Pattern: aws service-quotas list-service-quotas --service-code eks|ec2 -> verify headroom before cluster or ASG growth
  7. Pattern: aws resourcegroupstaggingapi tag-resources with CostCenter/Environment/Owner -> Cost Explorer filterable spend attribution
  8. Pattern: aws cloudformation deploy / cdk deploy with tags and terminationProtection -> reproducible console replacement
  9. Pattern: deny ec2:RunInstances / rds:CreateDBInstance via budget action SCP when forecast > budget -> credit burn prevention
  10. Pattern: never use root user access keys; break-glass MFA root only -> everyday ops via Identity Center roles
  11. Pattern: aws --version must show aws-cli/2.x from official installer -> reject unofficial package-manager CLI v1 drift
  12. Pattern: export AWS_PROFILE + AWS_REGION explicitly in CI/k8s Jobs -> no silent default-profile cross-account mistakes

Deeper fields

jq -r '.mission, .expertise, .keywords' "mcp/AI-LEGIOX/legiox-truth-lens/aws-console-cli-agent.nodus.json"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free