Menganalisis resource AWS dan file IaC untuk mengidentifikasi peluang penghematan biaya serta membuat GitHub issues terkait untuk implementasi.
- Bintang GitHub
- 41.038
- File
- 1
- Commit terakhir
- 11 Nov 2026
- Lisensi
- MIT
- Tool yang diizinkan
- —
Apa fungsi skill aws-cost-optimize?
Menganalisis resource AWS dan file IaC untuk mengidentifikasi peluang penghematan biaya serta membuat GitHub issues terkait untuk implementasi.
Ringkasan dibuat dari SKILL.md skill ini.
Tentang skill aws-cost-optimize
Skill ini memungkinkan DevOps engineer dan cloud architect untuk mengidentifikasi cara mengurangi pengeluaran cloud dengan menganalisis infrastruktur. Tool ini memeriksa lingkungan AWS Anda dengan memindai resource aktif seperti instance EC2, database RDS, fungsi Lambda, dan S3 bucket, bersamaan dengan file Infrastructure-as-Code Anda seperti Terraform atau CloudFormation. Dengan menggabungkan metrik penggunaan real-time dari CloudWatch dengan data billing historis dari Cost Explorer, tool ini mengidentifikasi pola spesifik di mana Anda melakukan over-provisioning atau menggunakan konfigurasi yang tidak efisien.
Setelah analisis selesai, skill ini menyajikan ringkasan potensi penghematan bulanan dan tingkat risiko untuk persetujuan Anda. Setelah dikonfirmasi, tool ini secara otomatis membuat rangkaian GitHub issues yang terstruktur untuk melacak pekerjaan tersebut. Ini mencakup tugas individual untuk setiap optimasi spesifik dan satu master EPIC issue untuk mengoordinasikan seluruh inisiatif penghematan biaya. Tool ini mengandalkan AWS CLI yang sudah dikonfigurasi dan MCP server GitHub yang terhubung untuk menjalankan tindakan ini.
Apa yang bisa dilakukan agent dengannya
- 1Automasi audit biaya cloudSeorang engineer dapat meminta pemindaian penuh pada akun AWS mereka untuk menemukan resource yang kurang dimanfaatkan dan menghasilkan tugas-tugas yang dapat langsung dikerjakan.
- 2Mengubah penghematan manual menjadi tugas yang terlacakSeorang developer dapat mengubah perbaikan infrastruktur yang telah diidentifikasi menjadi workflow yang terkelola di dalam repositori GitHub.
- 3Validasi infrastruktur terhadap best practicesPengguna dapat memastikan setup AWS mereka saat ini selaras dengan dokumentasi manajemen biaya resmi dan pilar well-architected.
Ditulis dari SKILL.md milik skill tersebut. Setiap use case diverifikasi dengan kutipan darinya.
Cara install skill aws-cost-optimize
Setiap perintah menyalin folder skill ke direktori skills client. Restart client atau mulai sesi baru untuk memuatnya.Install skill aws-cost-optimize di Claude Code
~/.claude/skills/aws-cost-optimize/SKILL.md
$ npx degit github/awesome-copilot/skills/aws-cost-optimize ~/.claude/skills/aws-cost-optimizeInstall skill aws-cost-optimize di Claude Code (project)
.claude/skills/aws-cost-optimize/SKILL.md
$ npx degit github/awesome-copilot/skills/aws-cost-optimize .claude/skills/aws-cost-optimizeInstall skill aws-cost-optimize di Codex
~/.agents/skills/aws-cost-optimize/SKILL.md
$ npx degit github/awesome-copilot/skills/aws-cost-optimize ~/.agents/skills/aws-cost-optimizeInstall skill aws-cost-optimize di Gemini CLI
~/.gemini/skills/aws-cost-optimize/SKILL.md
$ npx degit github/awesome-copilot/skills/aws-cost-optimize ~/.gemini/skills/aws-cost-optimizeInstall skill aws-cost-optimize di Claude.ai
npx degit github/awesome-copilot/skills/aws-cost-optimize aws-cost-optimize && zip -r aws-cost-optimize.zip aws-cost-optimize # claude.ai → Customize → Skills → + → Create skill → Upload a skill → aws-cost-optimize.zip
Pengecekan otomatis
Berjalan 15 Nov 2026Laporan lengkap →Lolos cek otomatis kami. Ini bukan audit keamanan: baca skripnya sebelum membiarkan agent menjalankannya. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkaugithub/awesome-copilot/skills/aws-cost-optimize is public and reachablegithub.com/github/awesome-copilot/tree/HEAD/skills/aws-cost- ↗Lolos
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit 2026-11-11github.com/github/awesome-copilot/commits ↗Lolos
- Skrip tanpa unduh-lalu-jalankan atau pencurian kredensialNo scripts in the skill folderLolos
- Tidak ada instruksi tersembunyi di SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/github/awesome-copilot/blob/HEAD/skills/aws-cost- ↗Lolos
- Tool yang diizinkan otomatis dibatasiNo pre-approved tools; the agent asks before using onegithub.com/github/awesome-copilot/blob/HEAD/skills/aws-cost- ↗Lolos
- SKILL.md mengikuti format Agent Skillsthe description does not say when to use the skillgithub.com/github/awesome-copilot/blob/HEAD/skills/aws-cost- ↗Temuan
SKILL.md
Lihat di GitHubAWS Cost Optimize
This workflow analyzes Infrastructure-as-Code (IaC) files and AWS resources to generate cost optimization recommendations. It creates individual GitHub issues for each optimization opportunity plus one EPIC issue to coordinate implementation, enabling efficient tracking and execution of cost savings initiatives.
Prerequisites
- AWS CLI configured and authenticated (
aws sts get-caller-identitysucceeds) - GitHub MCP server configured and authenticated
- Target GitHub repository identified
- AWS resources deployed (IaC files optional but helpful)
Workflow Steps
Step 1: Get AWS Cost Optimization Best Practices
Action: Retrieve cost optimization best practices before analysis
Tools: fetch to retrieve AWS documentation
Process:
- Load Best Practices:
- Fetch
https://docs.aws.amazon.com/cost-management/latest/userguide/cost-optimization-best-practices.html - Fetch the AWS Well-Architected Cost Optimization pillar summary
- Use these practices to inform subsequent analysis and recommendations
- Fetch
Step 2: Discover AWS Infrastructure
Action: Dynamically discover and analyze AWS resources and configurations Tools: AWS CLI + Local file system access Process:
-
Account & Region Discovery:
- Execute
aws sts get-caller-identityto confirm account - Execute
aws configure get regionto determine default region
- Execute
-
Resource Discovery (per region):
- EC2 instances:
aws ec2 describe-instances --query 'Reservations[].Instances[].[InstanceId,InstanceType,State.Name,Tags]' - RDS instances:
aws rds describe-db-instances --query 'DBInstances[].[DBInstanceIdentifier,DBInstanceClass,Engine,MultiAZ]' - Lambda functions:
aws lambda list-functions --query 'Functions[].[FunctionName,Runtime,MemorySize,Architectures]' - ECS clusters/services:
aws ecs list-clustersthenaws ecs describe-services - S3 buckets:
aws s3api list-buckets --query 'Buckets[].Name' - ElastiCache clusters:
aws elasticache describe-cache-clusters - NAT Gateways:
aws ec2 describe-nat-gateways - Load Balancers:
aws elbv2 describe-load-balancers
- EC2 instances:
-
IaC Detection:
- Scan for IaC files:
**/*.tf,**/*.yaml(CloudFormation/SAM),**/*.json(CloudFormation),**/cdk.json,lib/**/*.ts(CDK) - Parse resource definitions to understand intended configurations
- Do NOT use application code files — only IaC files as the source of truth
- If no IaC files found: STOP and report to user
- Scan for IaC files:
Step 3: Collect Usage Metrics & Validate Current Costs
Action: Gather utilization data and verify actual resource costs Tools: AWS CLI (CloudWatch, Cost Explorer) Process:
-
CloudWatch Metrics (last 7 days):
# EC2 CPU utilization aws cloudwatch get-metric-statistics \ --namespace AWS/EC2 --metric-name CPUUtilization \ --dimensions Name=InstanceId,Value=<id> \ --start-time $(date -u -d '7 days ago' +%Y-%m-%dT%H:%M:%SZ) \ --end-time $(date -u +%Y-%m-%dT%H:%M:%SZ) \ --period 3600 --statistics Average # Lambda duration aws cloudwatch get-metric-statistics \ --namespace AWS/Lambda --metric-name Duration \ --dimensions Name=FunctionName,Value=<name> \ --start-time $(date -u -d '7 days ago' +%Y-%m-%dT%H:%M:%SZ) \ --end-time $(date -u +%Y-%m-%dT%H:%M:%SZ) \ --period 86400 --statistics Average,Maximum -
AWS Cost Explorer:
aws ce get-cost-and-usage \ --time-period Start=$(date -u -d '30 days ago' +%Y-%m-%d),End=$(date -u +%Y-%m-%d) \ --granularity MONTHLY --metrics BlendedCost \ --group-by Type=DIMENSION,Key=SERVICE -
Calculate Baseline Metrics: CPU/Memory averages, Lambda invocation rates, data transfer patterns, and a realistic current monthly total.
Step 4: Generate Cost Optimization Recommendations
Action: Analyze resources to identify optimization opportunities Process:
-
Apply Optimization Patterns:
Compute:
- EC2: Right-size based on CPU/memory (<20% average → downsize), convert On-Demand to Savings Plans, migrate to Graviton/ARM (up to 40% cheaper)
- Lambda: Reduce memory for idle functions, switch to
arm64(20% cheaper) - ECS/EKS: Use Fargate Spot for dev/batch workloads
Database:
- RDS: Right-size instance class, convert single-AZ for dev, use Aurora Serverless v2 for variable load
- DynamoDB: Switch Provisioned → On-Demand for unpredictable traffic
- ElastiCache: Right-size node type based on memory utilization
Storage:
- S3: Lifecycle policies (Standard → Standard-IA after 30d → Glacier after 90d), enable Intelligent-Tiering
- EBS: Delete unattached volumes, convert gp2 → gp3 (same performance, 20% cheaper)
Network:
- Consolidate NAT Gateways for non-production environments
- Use VPC endpoints for S3/DynamoDB to avoid NAT Gateway charges
-
Calculate Priority Score:
Priority Score = (Value Score × Monthly Savings) / (Risk Score × Implementation Days) High: Score > 20 | Medium: Score 5-20 | Low: Score < 5
Step 5: User Confirmation
Action: Present summary and get approval before creating GitHub issues
🎯 AWS Cost Optimization Summary
📊 Analysis Results:
• Total Resources Analyzed: X
• Current Monthly Cost: $X
• Potential Monthly Savings: $Y
• Optimization Opportunities: Z
• High Priority Items: N
🏆 Recommendations:
1. [Resource]: [Current] → [Target] = $X/month savings - [Risk] | [Effort]
...
💡 This will create Y individual GitHub issues + 1 EPIC issue.
❓ Proceed with creating GitHub issues? (y/n)
Wait for user confirmation before proceeding.
Step 6: Create Individual Optimization Issues
Action: Create separate GitHub issues for each optimization. Label with "cost-optimization" (green) and "aws" (orange).
Title: [COST-OPT] [Resource Type] - [Brief Description] - $X/month savings
Body:
## 💰 Cost Optimization: [Brief Title]
**Monthly Savings**: $X | **Risk Level**: [Low/Medium/High] | **Effort**: X days
### 📋 Description
[Clear explanation of the optimization and why it's needed]
### 🔧 Implementation
**IaC Files Detected**: [Yes/No]
```bash
# IaC modification (preferred) or AWS CLI fallback
```
### 📊 Evidence
- Current Configuration: [details]
- Usage Pattern: [evidence from CloudWatch]
- Cost Impact: $X/month → $Y/month
### ✅ Validation Steps
- [ ] Test in non-production environment
- [ ] Verify no performance degradation via CloudWatch
- [ ] Confirm cost reduction in AWS Cost Explorer
### ⚠️ Risks & Considerations
- [Risk and mitigation]
**Priority Score**: X | **Value**: X/10 | **Risk**: X/10
Step 7: Create EPIC Coordinating Issue
Action: Create master tracking issue. Label with "cost-optimization" (green), "aws" (orange), "epic" (purple).
Title: [EPIC] AWS Cost Optimization Initiative - $X/month potential savings
Body: Executive summary with account/region details, Mermaid architecture diagram of current resources, prioritized checklist linking all individual issues (High → Medium → Low), progress tracking, and success criteria (>80% of estimated savings realized, no performance degradation).
Error Handling
- AWS Authentication Failure: Guide through
aws configure - No Resources Found: Create informational issue about AWS resource deployment
- Insufficient Permissions: List required IAM read-only permissions
- GitHub Creation Failure: Output formatted recommendations to console
- Cost Explorer Not Enabled: Guide user to enable in AWS Console
Success Criteria
- ✅ All cost estimates verified against actual configurations and AWS pricing
- ✅ Individual GitHub issues created for each optimization
- ✅ EPIC issue provides comprehensive coordination and tracking
- ✅ All recommendations include specific AWS CLI or IaC commands
- ✅ User confirmation obtained before creating issues
Berkas dalam skill ini
1Pertanyaan seputar skill aws-cost-optimize
Bagaimana cara install skill aws-cost-optimize di Claude Code?
Jalankan npx degit github/awesome-copilot/skills/aws-cost-optimize ~/.claude/skills/aws-cost-optimize. Claude Code memuat skill dari ~/.claude/skills (semua proyek) atau .claude/skills (satu proyek) dan menggunakan skill saat deskripsinya cocok dengan tugas.
Client mana saja yang bisa menggunakan skill aws-cost-optimize?
Client apa pun yang membaca format Agent Skills: Claude Code, Codex, Gemini CLI, dan claude.ai (unggah sebagai ZIP). Script dalam skill hanya berjalan di client yang mengizinkan eksekusi kode.
Bagaimana tool ini mengidentifikasi peluang optimasi?
Tool ini mengambil best practices AWS, mendeteksi infrastruktur melalui CLI dan file IaC, mengumpulkan metrik penggunaan dari CloudWatch, serta menerapkan pola optimasi khusus untuk resource compute, database, storage, dan network.