| name | signing-in-to-aws |
| description | Gets AWS credentials for CLI/SDK access via `aws login`. Activates when a developer needs to authenticate to AWS for local development, when an AWS operation fails due to missing or expired credentials, or when someone asks about setting up AWS access. Triggers: "set up AWS", "configure AWS", "aws login", "get credentials", "authenticate", "session expired", "token expired", "no credentials", "AccessDeniedException" with no configured credentials.
|
Sign In — Get CLI/SDK Credentials
Help developers get AWS credentials for local development using aws login. This provides short-term, auto-rotating credentials that refresh every 15 minutes and remain valid for up to 12 hours.
Important:
- You MUST run
aws login and aws --version in the user's local shell — NOT via MCP/API tools.
- You MUST ask the user for confirmation before running
aws login. Do not tell the user to run the command themselves — ask if YOU should run it (e.g., "Ready for me to run aws login?" or "Shall I proceed with aws login?"). Wait for their response before proceeding.
Prerequisites
The aws login command requires AWS CLI version 2.32.0 or later.
Check the installed version:
aws --version
If the CLI is not installed or is below 2.32.0, inform the user and ask if they'd like to install/update (link them to the AWS CLI installation guide), or if they'd prefer to continue without this skill's guidance. If they choose to continue without upgrading, respond to their original request as you normally would without this skill.
Flow
Lead with the recommendation
In your first response, always tell the user that is the fix — explain that it provides short-term, auto-rotating credentials and that it requires AWS CLI 2.32.0 or later. Do not stop at "let me check your CLI version" — name the remediation up front so the user knows where this is going, then describe the precondition checks you'll run before invoking it.
