IntermediateFinOps: Cloud Cost Management project · about 6 hours

Cost visibility and tagging

Tag resources, build cost reports and show spend per team.

The real-world brief

A SaaS company cannot see which team spends what.

What you will build

  • A tagging standard
  • Untagged resources fixed
  • A cost report by team
  • A showback summary

Skills you will practise

Cost allocationTaggingReportingFinOps basics

Tools

AWS Cost Explorer or Azure Cost ManagementTagging policiesSpreadsheets or Power BI

Project tasks

The detailed steps, checklists and trainer review open in the SOTT student portal for enrolled students.

1Standard Steps in portal
2Enforce Steps in portal
3Report Steps in portal
4Share Steps in portal

How companies use FinOps: Cloud Cost Management

SaaS: Cloud bill under control. The cloud bill grew 40 percent in a year and nobody knew why. Tagging, showback per team, rightsizing and commitments. Spend dropped while usage grew.

Retail: Paying for idle test environments. Test servers ran all weekend. Schedules to stop idle resources and budget alerts. Non-production costs fell sharply.

Fintech: Unit costs. Leaders could not see cost per customer. Cost per transaction dashboards from tagged spend. Pricing decisions now use real unit costs.

Questions

Can I add the Cost visibility and tagging project to my resume?

Yes. Once your trainer approves it, list it under Projects with the tools you used, one line on the problem it solves and a link to your repository and demo video.

How long does this project take?

About 6 hours of hands-on work, and it fits best after week 2 of the FinOps: Cloud Cost Management course.

Where do I get the step-by-step tasks?

Enrolled students get every task with steps, "done when" checks, the submission form and a trainer review in the SOTT student portal.