Official-source guidance
Every practice links back to an AWS-owned source such as AWS documentation, AWS blogs, or Well-Architected content.
Claude Code and OpenAI Codex skill
AWS Best Practices Skill
An unofficial, source-linked catalog of AWS-published best practices that coding agents can read directly and tailor to the user's scenario, without relying on stale model memory or repeated live research.
Independent community project. Not an official AWS skill, AWS product, or AWS-maintained resource; not affiliated with or endorsed by Amazon Web Services.
208
AWS services
9
general AWS topics
217
best-practice files
30.51M
tracked generation tokens
What it is
Best practices only, organized for agent workflows
Well-Architected shape
Service files are grouped by security, reliability, performance efficiency, cost optimization, operational excellence, and sustainability.
Focused scope
The corpus intentionally excludes service descriptions, pricing, tutorials, and long code samples so an agent can answer quickly and stay on task.
Scenario-targeted answers
Agents use the local common-scenarios map first, then return the relevant baseline, decisions, and caveats instead of dumping every practice.
Coverage
A catalog built around the AWS service taxonomy
The repository stores a machine-readable source of truth in catalog.json, a human index in catalog.md, and one Markdown file per service or general topic.
Security, Identity & Compliance 23
Management & Governance 20
Machine Learning 19
Analytics 18
Networking & Content Delivery 16
Database 14
Compute 11
Storage 10
Developer Tools 10
IoT 9
General AWS Best Practices 9
Application Integration 9
Media Services 8
Containers 7
Business Applications 7
Migration & Transfer 7
Cloud Financial Management 6
Front-End Web & Mobile 5
End User Computing 4
Game Tech 2
Blockchain 1
Quantum Technologies 1
Satellite 1
Extraction process
How new best-practice files are created
-
Read the catalog scope.
GENERATE.mdstarts from missing entries incatalog.json, optionally limited to one AWS category. - Research only official AWS sources. The agent searches AWS documentation, Well-Architected content, and AWS-owned pages for service-specific best practices.
- Normalize the result. Each file gets common scenarios, relevant Well-Architected pillar sections, context tags, concise imperatives, and source links.
- Reject noisy content. Descriptions, pricing, tutorials, and extended code samples are removed because the skill is a best-practices corpus, not a general AWS manual.
-
Validate and index.
scripts/check.pychecks conformance, coverage, link hosts, freshness metadata, and regeneratescatalog.mdplus theSKILL.mdindex.
Update process
How the catalog avoids becoming stale
-
Diff the AWS service lineup.
REFRESH.mdcompares the current AWS product list withcatalog.jsonbefore touching existing content. - Classify catalog drift. New, renamed, recategorized, and fully retired services are handled differently so the catalog does not duplicate or prematurely delete services.
- Refresh stale entries. Files older than the freshness threshold, currently 180 days by default, are re-reviewed against current official AWS guidance.
-
Run local gates before publishing.
Maintainers use
python3 scripts/check.py,--strict,--check-links, and--staleto keep the catalog complete and sourced.
Install and validate
Use it as a plugin or clone it as a skill
Claude Code
claude plugin marketplace add ferdinandobons/AWSBestPracticesSkill
claude plugin install aws-best-practices@aws-best-practices-skillOpenAI Codex CLI
codex plugin marketplace add ferdinandobons/AWSBestPracticesSkill
codex plugin add aws-best-practices@aws-best-practices-skillMaintainer checks
python3 scripts/check.py
python3 scripts/check.py --strict
python3 scripts/check.py --check-links
python3 scripts/check.py --staleSource files