aws-cost-operations
AWS cost/ops quick guide for budgeting, monitoring, and optimization with standard guardrails.
- License 许可
- MIT
- 最近更新
- 2026-08-03
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- aws-cost-operations
- description
- AWS cost/ops quick guide for budgeting, monitoring, and optimization with standard guardrails.
02 资源文件 3
- 脚本evals/evals.js61.2 KB
- 参考文档references/cloudwatch-alarms.md13.4 KB
- 参考文档references/operations-patterns.md10.2 KB
03 SKILL.md 正文
AWS Cost & Operations (Concise)
Use for: FinOps reviews, budget/alerts, right-sizing, and ops hygiene on AWS.
Core steps
- Accounts/guardrails: org SCPs, SSO, budgets per OU; tag standards (owner, env, cost-center, app).
- Budgets/alerts: AWS Budgets + SNS/Email/Chat; anomaly detection on Cost Explorer; set % thresholds.
- Right-size: compute (EC2/ASG/Fargate/Lambda) based on utilization; S3/Glacier lifecycle; RDS/Aurora rightsizing; turn off idle.
- Pricing levers: Savings Plans/RIs, Graviton preference, spot where safe, data transfer minimization (VPC endpoints, regional design).
- Storage: S3 IA/Glacier policies; EBS GP3; snapshots lifecycle; DynamoDB autoscaling + TTL.
- Networking: prune NAT gateways, use private links/endpoints, limit cross-AZ and inter-region flows.
- Observability: tag propagation to logs/metrics; cost per service/app dashboards; alarms on spend and on disabled logging.
Ops hygiene
- Enable CloudTrail, Config, GuardDuty, Security Hub; centralize logs (KMS, retention).
- IaC: use CDK/Terraform with reviews and drift checks.
- Backup/DR: retention policies, periodic recovery tests.
Quick checks
aws ce get-cost-and-usagefor recent spikes; check untagged spend.- S3
storage-lens,s3 ls --summarize; EBS snapshot list/age; idle load balancers; idle RDS/ElastiCache.
References
- AWS Well-Architected Cost pillar; AWS Budgets/CE docs; FinOps best practices.
04 同仓库更多 Skills
next-workflow-step
Use this skill when the user wants to transition to the next workflow step, wrap up a session cleanly, prepare a handoff, or says things like "next step", "continue the workflow", "wrap up", "hand off", "move to the next phase", "what's next in embrace", or "prepare for /clear". Also triggers when the current octo:embrace phase appears complete and no explicit next action is set.
source-discovery
This skill should be used when the user asks to "find sources", "discover URLs", "catalog a source", "classify a URL", "search for libraries", "check what exists", or mentions source discovery, URL cataloging, source classification, or research source management.
review-synthesis
This skill should be used when the user asks to "summarize review findings", "prioritize fixes", "rank review issues", "combine reviewer feedback", "create action items from review", or mentions review synthesis, finding prioritization, severity ranking, or review result summarization.
research-scoring
This skill should be used when the user asks to "score research", "check research quality", "evaluate coverage", "measure improvement", "assess research completeness", or mentions research scoring, quality metrics, coverage gaps, improvement baseline, or research pipeline status.
notebooklm-integration
This skill should be used when the user asks to "ingest into NotebookLM", "query NotebookLM", "add sources to notebook", "cross-source synthesis", "check stale sources", or mentions NotebookLM, notebook integration, source ingestion, or knowledge consolidation.
evidence-synthesis
This skill should be used when the user asks to "synthesize findings", "combine research", "cross-reference sources", "summarize evidence", "write a deep review", or mentions evidence synthesis, finding consolidation, cross-source analysis, or research summarization.