aws-sqs-sns
Use when using AWS messaging.
SKILL.mdskills/aws-sqs-sns/SKILL.md
GitHubAws Sqs Sns
"Use when using AWS messaging."
Trigger
Activate this skill when the user mentions:
- cloud, aws, aws-sqs workflows or issues
- Building, fixing, or optimizing aws sqs sns
- Questions about cloud best practices
Core Concepts
- Infrastructure as Code (IaC)
- Well-Architected Framework
- Identity and access management
- Networking and security groups
- Cost optimization and tagging
Step-by-Step Workflow
- Design — Architecture review against WAF pillars
- Expected: Approved architecture diagram
- Implement — IaC templates with least-privilege IAM
- Expected: Reviewable version-controlled infra
- Validate — Security scan, cost estimate, plan review
- Expected: Clean plan within budget
- Deploy — Apply with change management
- Expected: Deployed infrastructure matches plan
- Monitor — Alarms, dashboards, cost alerts
- Expected: Full observability and cost allocation
Tools & Technologies
- Terraform/Pulumi
- Cloud-native IaC
- Security scanning
- Cost management
Best Practices
- Document decisions and rationale (ADRs, design docs, runbooks)
- Version everything - code, configs, data, and documentation
- Test incrementally; never claim passing without verification
- Respect domain-specific regulations and ethical standards
- Measure outcomes with meaningful metrics
Common Pitfalls
- Manual console changes → Configuration drift → All changes through IaC
- Over-privileged IAM → Blast radius risk → Least privilege by default
Tags
cloud, aws, aws-sqs
LoopyLuci/Skills - 2026-09-24