We often fall into the misconception that cost is a proxy for carbon emissions in cloud computing. The assumption seems logical: if we spend less on a public cloud, we're presumably using fewer resources and emitting less CO2. However, this assumption can be misleading. For instance, the choice of region for hosting virtual machines can drastically impact carbon emissions, even if the cost per hour remains similar across regions

FinOps practices can help us understand and reducing the costs of cloud infrastructure, thanks to cloud automation. "GreenOps" has been coined, with the same idea: using DevOps and FinOps practices to reduce CO2 emissions and other impacts of a cloud infrastructure.
Finally, I will demonstrate how to use tools to help estimate the costs and impacts of a cloud infrastructure.