Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From AWS Best Practices
Local catalog of AWS best practices organized by service and Well-Architected pillar. Answers configuration, hardening, and optimization questions without live web searches.
How this skill is triggered — by the user, by Claude, or both
Slash command
/aws-best-practices:aws-best-practicesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A curated, source-linked collection of **AWS best practices** for every AWS
A curated, source-linked collection of AWS best practices for every AWS service, plus cross-service general guidance. Organized so you can find what matters for a specific use case.
No live web for ordinary answers: use the local files in this repository. Do not search the web, open AWS documentation URLs, or use live documentation tools unless the user explicitly asks for a current/live refresh or the local catalog is missing the requested service/topic.
Unofficial project: this skill is independently maintained. It is not an official AWS skill, AWS product, or AWS-maintained resource, and it is not affiliated with or endorsed by Amazon Web Services.
[when-it-applies] context and linked to
the official AWS source.catalog.md (or the index below) and find the service's
file path.services/<category>/<service>.md.## Common scenarios block first to map the use case to the
relevant pillars, then read those pillar sections. Each bullet's
[context] tag tells you whether it applies to the user's situation.general/.For ordinary best-practice answers, use this repository as the source of truth:
read SKILL.md, catalog.md, and the relevant local services/ or general/
file. Do not call web search, open AWS documentation URLs, fetch pages, or
use live documentation tools just to verify or cite a bullet that is already in
the local file. The [doc](...) URLs in those files are pre-recorded citations:
copy them from the local Markdown when useful, but do not visit them.
Use live web/documentation access only when the user explicitly asks for a current/live refresh, asks you to verify whether AWS changed something, or when the requested service/topic is not covered by the local catalog.
If a service is not yet covered, say so plainly; do not invent best practices.
Prefer a targeted answer over an exhaustive dump. If the user gives a specific scenario, workload, constraint, or concern, select only the best practices that apply to that case.
Examples:
If the user does not provide a specific scenario, give the general production baseline for that service: the most broadly useful practices across Security, Reliability, Performance Efficiency, Cost Optimization, and Operational Excellence. Do not list every bullet in the file unless the user asks for a complete/deep-dive answer.
Default to an actionable production baseline, not an encyclopedia. Use this shape unless the user asks for another format:
Avoid very wide tables by default because they often wrap poorly in terminals. Use compact bullets unless the user explicitly asks for a table.
services/<category>/<service>.md # per-service best practices (pillar-organized)
general/<topic>.md # cross-service best practices
catalog.md # human index (generated)
catalog.json # machine-readable source of truth
npx claudepluginhub ferdinandobons/awsbestpracticesskill --plugin aws-best-practicesProvides deep AWS expertise for IAM policies, VPC networking, EKS/ECS/Lambda compute, RDS/DynamoDB/S3 storage, security hardening, monitoring, and multi-account production strategies.
Conducts formal AWS Well-Architected Framework reviews against workloads, evaluating architecture across six pillars, identifying high-risk issues, and creating improvement plans.
Provides structured AWS cost optimization via five pillars (right-sizing, elasticity, pricing, storage, monitoring) and 12 best practices with AWS CLI examples. For reviewing spending, unused resources, FinOps.