Что такое FinOps

• Tagging: каждый resource имеет owner + project tags
• Dashboards: по команде, проекту, environment — кто сколько тратит
• Savings instruments: AWS Reserved Instances, Savings Plans, Committed Use Discounts
• Right-sizing: unused EC2 instances → смaller type
• Spot/preemptible: 60-90% cheaper для batch workloads

AWS cost example:
- Tag: Project=enterno, Env=prod
- EC2 on-demand:        $100/month
- EC2 3-year RI:        $35/month  (-65%)
- Spot (batch jobs):    $15/month  (-85%)

• SRE
• Observability

Key metrics in FinOps are essential for measuring and optimizing cloud spending. These metrics help teams understand usage patterns, identify cost inefficiencies, and make data-driven decisions. Some key metrics include:

• Cost per Unit of Work: Measures the cost associated with a specific task or workload. For example, the cost per instance-hour or the cost per API call.
• Utilization Rate: Indicates how much of a resource is being used compared to its total capacity. High utilization rates can indicate efficient use of resources, while low rates might suggest underutilization and potential cost savings.
• Cost Variance: Compares actual costs to budgeted or forecasted costs. A positive variance indicates overspending, while a negative variance suggests cost savings.
• Return on Investment (ROI) of Cloud Services: Measures the financial return generated from cloud investments compared to the costs incurred. A high ROI indicates efficient use of cloud resources.

Practical Example: To monitor cost per unit of work, teams can use AWS Cost Explorer to track instance-hours and API calls, then calculate the cost associated with each.

Several tools are available to help manage cloud costs and implement FinOps practices. These tools can assist in tagging, monitoring, optimizing, and automating cloud spending. Some popular tools include:

• AWS Cost Explorer: Provides visualizations and reports on AWS spending, helping teams identify cost trends and optimize resource usage.
• Azure Cost Management: Offers tools for monitoring, allocating, and optimizing Azure spending, with features like budgets and alerts.
• Google Cloud Billing: Provides insights into Google Cloud spending, with features for budgeting, forecasting, and cost management.
• Third-party tools: Tools like CloudHealth, Kyribo, and Datadog can provide comprehensive FinOps solutions by integrating with multiple cloud providers and offering advanced analytics.

Practical Example: To set up cost alerts in AWS, teams can use AWS Budgets to create budgets based on cost metrics like cost per instance-hour, and receive alerts when spending approaches the budget limit.

Implementing FinOps can present several challenges that teams need to overcome to effectively manage cloud costs. Some common challenges include:

• Lack of Visibility: Many organizations struggle with visibility into their cloud spending due to complex multi-cloud environments and diverse resource types. This lack of visibility makes it difficult to identify cost inefficiencies.
• Siloed Teams: Often, finance teams and engineering teams work in isolation, leading to misalignment in cost management strategies. FinOps requires collaboration between these teams to optimize spending.
• Complexity of Cloud Providers: Cloud providers offer a wide range of services and features, which can be overwhelming for teams to manage. Understanding and optimizing these services to reduce costs requires expertise.
• Resistance to Change: Teams may resist changing established processes and practices, even if these changes could lead to significant cost savings. Overcoming this resistance requires strong leadership and communication.

Practical Example: To address lack of visibility, teams can implement tagging strategies to categorize and track spending by project, team, or other relevant dimensions, using tools like AWS Resource Tags or Azure Tags.