https://github.com/shauryashaurya/finops-and-find-out
https://github.com/shauryashaurya/finops-and-find-out
aws azure cloud cost-and-usage-report finops finops-framework gcp kpi pyspark python
Last synced: 3 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/shauryashaurya/finops-and-find-out
- Owner: shauryashaurya
- License: gpl-3.0
- Created: 2025-03-31T17:25:19.000Z (6 months ago)
- Default Branch: main
- Last Pushed: 2025-03-31T18:49:04.000Z (6 months ago)
- Last Synced: 2025-06-28T22:48:14.061Z (3 months ago)
- Language: Python
- Size: 19.1 MB
- Stars: 0
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# FinOps and find out...
An indepth exploration of Cost and Usage data across AWS, GCP and Azure.
All data is notional (and generators for the data are included).
We perform all sorts of analysis, including chargeback, showback and others.
We try to build models to forecast costs by projects, services etc.
Possibly even try our hand at scenario based analysis too.
# Data, Data Dictionaries, Comparisions and Data Generators
The repo has minimal data for each (as I want to avoid getting into GitHub LFS).
Fork/download the repo and run the data generators.
Every generator has a ```DATA_VOLUME_SETTINGS``` dict that can be configured to generate more projects.
Each of the generators has a `_config.py` where more details about the services, the projects, account hierarchies etc. can be configured as well.
* [AWS](https://github.com/shauryashaurya/FinOps-and-find-out/tree/main/cost-and-usage-data/aws)
* [GCP](https://github.com/shauryashaurya/FinOps-and-find-out/tree/main/cost-and-usage-data/gcp)
* [Azure](https://github.com/shauryashaurya/FinOps-and-find-out/tree/main/cost-and-usage-data/azure)
* [**Multi-Cloud** Setup (a mix of GCP, Azure and AWS)](https://github.com/shauryashaurya/FinOps-and-find-out/tree/main/cost-and-usage-data/multi) - this uses the data generators from the AWS, GCP and Azure modules. This was incredibly complex, and frankly a bit frustrating to build - I can totally relate to the FinOps teams dealing with multiple cloud based environments at the same time, esp. in large enterprises... Once this code worked, it was so much fun! :) :) :)
.