# AWS CLI

> Use the correct AWS CLI profile when running AWS commands based on the target environment.

- Skill: `abdullahkhawer/aws-cli` (Agent Skill)
- Install (CLI): `npx skillmds@latest add abdullahkhawer/aws-cli`
- Raw SKILL.md: https://api.skillmd.com/api/skills/abdullahkhawer/aws-cli/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: abdullahkhawer (https://skillmd.com/u/abdullahkhawer)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/abdullahkhawer/aws-cli

---


# AWS CLI Skill

When running AWS CLI commands, always pass the `--profile` flag based on the target environment.

## Configuration

Update the profile map below with your AWS profile names as configured in `~/.aws/config`:

| Environment | Profile |
|---|---|
| Production | `<your-prod-profile>` |
| Staging / Non-Prod | `<your-nonprod-profile>` |

## Command Format

```bash
aws <service> <command> --profile <profile> [options]
```

### Examples

```bash
# Production
aws s3 ls --profile my-prod-profile

# Staging / Non-Prod
aws s3 ls --profile my-nonprod-profile
```

## Rules

- Always specify `--profile` explicitly — never rely on the default profile.
- If the target environment is unclear, ask the user before running the command.