Overview
AWS infrastructure management covering core services (EC2, S3, Lambda, RDS), IAM security, CloudFormation IaC, and cost optimization strategies.
Capabilities
- EC2 instance management and auto-scaling
- S3 bucket policies and lifecycle
- Lambda function deployment
- IAM policy design
- CloudFormation templates
- Cost optimization (Spot, Reserved, Savings Plans)
- CloudWatch monitoring
When to Use
Trigger phrases:
"aws ops"
"AWS operations — EC2, S3, Lambda, RDS, ECS, IAM, CloudFormation"
Cloud infrastructure management
Web application hosting
Data processing pipelines
Cost optimization reviews
When NOT to Use
- Task is outside your authorization scope
- You need to implement controls (use implementing-* skills)
- Task is about analysis, not action (use analyzing-* skills)
- You don't have access to target systems
- Task requires compliance expertise (consult professionals)
- Task is about defense, not offense (use defensive skills)
Pseudo Code
The aws-ops workflow follows a standard pipeline pattern.
Core flow:
# aws-ops primary flow
input = prepare(raw_data)
result = process(input, config={aws, cloudformation, cost, infrastructure, lambda})
validate(result)
deliver(result)
Error handling:
on error:
log(error_details)
retry_with_backoff(max=3)
if still_failing: alert_and_escalate()
CloudFormation EC2
Resources:
WebServer:
Type: AWS::EC2::Instance
Properties:
InstanceType: t3.micro
ImageId: ami-0abcdef1234567890
SecurityGroupIds: [!Ref WebSG]
Tags:
- Key: Name
Value: WebServer
Common Patterns
- Tag everything for cost tracking
- Use IAM roles, not access keys
- Enable CloudTrail for audit
- S3 lifecycle rules for cost
How to Use
- Define infrastructure as code (Terraform, CloudFormation, Pulumi)
- Review changes through PR process before applying
- Configure monitoring and alerting for critical paths
- Set up secrets management (Vault, AWS Secrets Manager, etc.)
- Document runbooks for deployment, rollback, and incident response
- Test disaster recovery procedures regularly
Red Flags
- Infrastructure changes without review: Unreviewed changes cause outages — use PRs for infra code
- No rollback strategy: Every deployment needs a tested rollback plan before it runs
- Secrets in configuration files: Secrets in YAML/JSON get committed to version control
- Missing monitoring and alerting: Without monitoring, outages go undetected until users report them
- No documentation for runbooks: Without runbooks, on-call engineers waste time re-discovering procedures
Verification
Process
- Analyze the task requirements
- Apply domain expertise
- Verify output quality
Anti-Rationalization Table
| Rationalization |
Reality |
| "Manual deployments are fine" |
Manual deployments are error-prone and不可 repeatable. Automate. |
| "We do not need monitoring" |
Without monitoring, you are flying blind. Add observability from day one. |
| "Infrastructure as code is overkill" |
IaC enables reproducibility, version control, and disaster recovery. |
1---2name: aws-ops3description: Use when aWS operations — EC2, S3, Lambda, RDS, ECS, IAM, CloudFormation.4 Infrastructure and cost optimization. Use when working with aws ops.5domain: devops6author: oyi777license: Apache-2.08subdomain: devops9tags:10- aws11- ci-cd12- devops13- infrastructure14- ops15version: 1.0.016category: devops17metadata:18 source: https://skillmd.com/skills/oyi77/aws-ops19---20212223## Overview2425AWS infrastructure management covering core services (EC2, S3, Lambda, RDS), IAM security, CloudFormation IaC, and cost optimization strategies.2627## Capabilities2829- EC2 instance management and auto-scaling30- S3 bucket policies and lifecycle31- Lambda function deployment32- IAM policy design33- CloudFormation templates34- Cost optimization (Spot, Reserved, Savings Plans)35- CloudWatch monitoring3637## When to Use38**Trigger phrases:**39- "aws ops"40- "AWS operations — EC2, S3, Lambda, RDS, ECS, IAM, CloudFormation"414243- Cloud infrastructure management44- Web application hosting45- Data processing pipelines46- Cost optimization reviews4748## When NOT to Use4950- Task is outside your authorization scope51- You need to implement controls (use implementing-* skills)52- Task is about analysis, not action (use analyzing-* skills)53- You don't have access to target systems54- Task requires compliance expertise (consult professionals)55- Task is about defense, not offense (use defensive skills)565758## Pseudo Code5960The aws-ops workflow follows a standard pipeline pattern.6162Core flow:63```64# aws-ops primary flow65input = prepare(raw_data)66result = process(input, config={aws, cloudformation, cost, infrastructure, lambda})67validate(result)68deliver(result)69```7071Error handling:72```73on error:74 log(error_details)75 retry_with_backoff(max=3)76 if still_failing: alert_and_escalate()77```787980### CloudFormation EC281```yaml82Resources:83 WebServer:84 Type: AWS::EC2::Instance85 Properties:86 InstanceType: t3.micro87 ImageId: ami-0abcdef123456789088 SecurityGroupIds: [!Ref WebSG]89 Tags:90 - Key: Name91 Value: WebServer92```9394## Common Patterns9596- Tag everything for cost tracking97- Use IAM roles, not access keys98- Enable CloudTrail for audit99- S3 lifecycle rules for cost100101## How to Use1021031. Define infrastructure as code (Terraform, CloudFormation, Pulumi)1042. Review changes through PR process before applying1053. Configure monitoring and alerting for critical paths1064. Set up secrets management (Vault, AWS Secrets Manager, etc.)1075. Document runbooks for deployment, rollback, and incident response1086. Test disaster recovery procedures regularly109110## Red Flags111112- **Infrastructure changes without review**: Unreviewed changes cause outages — use PRs for infra code113- **No rollback strategy**: Every deployment needs a tested rollback plan before it runs114- **Secrets in configuration files**: Secrets in YAML/JSON get committed to version control115- **Missing monitoring and alerting**: Without monitoring, outages go undetected until users report them116- **No documentation for runbooks**: Without runbooks, on-call engineers waste time re-discovering procedures117118## Verification119120- [ ] Skill output matches expected behavior121122## Process1231241. Analyze the task requirements1252. Apply domain expertise1263. Verify output quality127128## Anti-Rationalization Table129130| Rationalization | Reality |131|---|---|132| "Manual deployments are fine" | Manual deployments are error-prone and不可 repeatable. Automate. |133| "We do not need monitoring" | Without monitoring, you are flying blind. Add observability from day one. |134| "Infrastructure as code is overkill" | IaC enables reproducibility, version control, and disaster recovery. |