aws

Amazon Web Services cloud platform with Lambda, EC2, S3, and RDS. Use for AWS infrastructure.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

aws is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Amazon Web Services cloud platform with Lambda, EC2, S3, and RDS. Use for AWS infrastructure.

Teams using aws should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/aws/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/devops/aws/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/aws/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How aws Compares

Feature / Agent	aws	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Amazon Web Services cloud platform with Lambda, EC2, S3, and RDS. Use for AWS infrastructure.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# AWS

Amazon Web Services (AWS) is the dominant cloud platform. In 2025, the focus is heavily on **Generative AI** (Bedrock, Q, Trainium chips) and **Serverless Data** (Aurora Limitless).

## When to Use

- **Enterprise**: The default choice for large-scale, compliant infrastructure.
- **AI/ML**: Amazon SageMaker and Bedrock provide the deepest toolset for training and inference.
- **Serverless**: Lambda + DynamoDB + API Gateway is the canonical serverless stack.

## Core Concepts

### VPC (Virtual Private Cloud)

Your isolated network. Subnets, Route Tables, Internet Gateways. Understanding networking is mandatory.

### IAM (Identity and Access Management)

Global service for permissions. "Deny by default". Use **Roles** for services, not access keys.

### Compute

- **EC2**: Virtual Machines.
- **ECS/EKS**: Containers (Docker/K8s).
- **Lambda**: Function-as-a-Service.

## Best Practices (2025)

**Do**:

- **Use AWS Organizations**: Separate Prod, Staging, and Dev into different _Accounts_, not just VPCs. Limits blast radius.
- **Use CDK / Terraform**: Never click in the console for production resources.
- **Cost Control**: Enable Cost Explorer and set up Budgets/Alerts on day one.

**Don't**:

- **Don't use Public Subnets for Apps**: Put your EC2s/RDS in Private Subnets. Only Load Balancers go in Public Subnets.

## References

- [AWS Documentation](https://docs.aws.amazon.com/)