Scope3 Emissions

[Harika vlog]

Hi Team,

while calculating the Embodied Emissions for AWS and AZURE instances we are getting null for some of the instance types due to missing scope3 emissions

From the CCF documentation we have gone through the Teads Engineering article, but we are unable to understand the process to calculate the scope3 emissions for the instance types, could you please explain  the process for any one of the instance type(c6id.24xlarge)

For Azure, could you please explain the process you followed to calculate the missing scope3 emissions for the instance types.

Thanks,

Harika

[Cloud Carbon Footprint]

Hi Harika,

It looks like you are getting unexpected null values. For this would you please consider opening up a bug report / new issue on our github repository with more detailed information to investigate this further?

For your second point, could you please elaborate if you are trying to understand the specific embodied emissions calculations or the more general compute estimations? If there is any part of our documentation that is not making sense, could you please let us know specifically so that we could look into updating it?

Lastly, if the instance type is missing, we consider this an unknown usage type. You can refer here for more information. If it is returning null, this would indeed be a bug.

Thanks,
CCF Team

[Harika vlog]

Thanks for the reply

Could you please explain how you have calculated the scope3 emissions for the AWS Instance Type(c6id.24xlarge) And Azure Instance Type(e32-16sv5).

Regards,

Harika