aws-finops

Guides AWS cost allocation, optimization, and governance using the FinOps Framework and FOCUS billing data.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/lurodrisilva/personal-skills --skill aws-finops-lurodrisilva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aws-finops
Source: https://github.com/lurodrisilva/personal-skills/tree/main/platform-engineering/aws-finops
Command: npx skills add https://github.com/lurodrisilva/personal-skills --skill aws-finops-lurodrisilva

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Cloud bills grow opaque and uncontrolled: spend is untagged, anomalies surface weeks late, and teams buy Savings Plans before right-sizing. This Skill provides the operating doctrine and AWS toolchain to allocate, understand, optimize, and govern AWS spend on a continuous cadence. ## Core Features & Use Cases - Cost allocation and reporting: Set up Data Exports in FOCUS format into S3 + Athena + QuickSight, cost allocation tags, Cost Categories, and Organizations hierarchy to reach 90% allocatable spend. - Usage and rate optimization: Triage rightsizing and idle waste with Compute Optimizer and Cost Optimization Hub, then size Savings Plans, Reserved Instances, Spot, and Graviton commitments against coverage and utilization targets. - Budgeting, forecasting, and governance: Configure AWS Budgets with actions, Cost Anomaly Detection, Billing Conductor chargeback, and SCP/tag-policy guardrails, plus EKS Split Cost Allocation Data and Bedrock/SageMaker unit economics. - Use Case: An engineer notices an overnight cost spike. Use this Skill to query Cost Explorer by service and account, run the read-only waste-finder script for unattached EBS volumes and unassociated Elastic IPs, then route findings into a gated, human-approved remediation change. ## Quick Start Ask the agent to analyze last month's AWS spend by service and linked account using Cost Explorer and identify idle or orphaned resources worth reviewing.

Frequently Asked Questions about aws-finops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find wasted AWS spend like unattached EBS volumes?▼

Run the read-only aws-waste-finder.sh script, which uses aws ec2 describe calls to list unattached EBS volumes, unassociated Elastic IPs, stopped instances, aged snapshots, and load balancers in a region. Confirm each candidate with its owner before any removal, which is always a separate gated change.

Savings Plans vs Reserved Instances: which should I use on AWS?▼

Compute Savings Plans are the default commitment for EC2, Fargate, and Lambda because they flex across instance families and Regions. Use Reserved Instances only where no Savings Plan exists, such as RDS, ElastiCache, Redshift, and OpenSearch, and always right-size usage before committing.

How do I allocate AWS costs to teams for showback or chargeback?▼

Activate user-defined cost allocation tags, define Cost Categories with split charge rules for shared costs, and use AWS Organizations account hierarchy as allocation boundaries. Target at least 90% allocatable spend, then use Billing Conductor for pro-forma chargeback with agreed markups.

What is FOCUS and how does it work with AWS billing data?▼

FOCUS is the FinOps Open Cost and Usage Specification, a vendor-neutral billing schema available through AWS Data Exports. It provides stable columns like BilledCost, EffectiveCost, and PricingCategory so the same Athena and QuickSight queries work across clouds.

Does a stopped EC2 instance still cost money?▼

Yes. A stopped EC2 instance stops billing for compute, but its attached EBS volumes and any associated Elastic IP continue to incur charges. Delete unattached storage and release idle IPs through a human-approved change to stop the spend.

What are the limitations of the aws-finops triage scripts?▼

The scripts are read-only starting points, not certified financial reports, and only run describe, get, and list calls. They require Cost Explorer read access (billed about $0.01 per API call), EC2 and ELB describe permissions, and Cost Optimization Hub opted in for the recommendations section.