Where exactly is the cut-off point between technical cloud operations and financial cloud operations?
The past years several paradigms have been embraced in the IT cloud operations landscape:
- The cloud engineer should be aware of security and work in a secure manner, including adopting secure practises such as MFA, key rotation and other services available to secure the daily operations.
- The cloud engineer should work according to the architectural best practises when deploying temporary/longterm resources in a public cloud provider.
But then..
Cloud engineer, should you be aware of what stuff costs?
Those two statements lead to the following question: Should the cloud engineer and cloud architect also be:
- aware of thee underlying cost of the resources and processes they spin up (thinking egress traffic)?
- monitor and report superfluous cloud resource usage that results in highr costs than necessary?
Could FinOps result in more corporate knowledge and transparency silos?
Furthermore, by creating a FinOps “dicsipline” where Financial teams in corporations are to calculate erronous usage of cloud resourses (erroneous in the context of “resultling in higher cost than necessary), another silo is created in companies which goes against the efforts to embrace cross-functional work and knowledgesharing.
Cloud architect and cloud engineer: The cloud spend is your responsibility
Does it not make sense that cloud architects and cloud engineers are responsible for cost optimization and cost awareness of the cloud resources used?