I agree that our tables are inconsistent for E2 (I sent an email about this internally, we'll try to get it fixed). tl;dr: You did calculate it right. $10.3/vC

I agree that our tables are inconsistent for E2 (I sent an email about this internally, we'll try to get it fixed). tl;dr: You did calculate it right. $10.3/vCPU/month x 2 vCPU + $1.34/GB/month x 8 GB for a 1-year commitment aka $30.78/month (and $22/month for a 3-year commitment). All of the predefined shapes are just "how many vCPUs times $/vCPU + how many GBs times $/GB". Ignoring the lack of columns for commitment pricing in the predefined shapes tables (which some instance types have and some don't... grr), I want to explain the reasoning. One thing that's different for GCP vs AWS is that we actually don't have a SKU for e2-standard-2 or e2-standard-16. We instead do "Resource Based Pricing" [1], and there's only "E2 Instance Core" and "E2 Instance Ram" or whatever. So if you have 100 e2-standard-2s and 100 e2-standard-16s running for a month, your bill will have two line items: - 1800 vCPUs times 2.6M seconds of Predefined E2 vCPU - 7200 GB times 2.6M seconds of Predefined E2 GB Memory The price for E2 is apparently the same ($10.03/vCPU/month) for both Custom vCPUs as well as Predefined vCPUs [2] (meaning the price for your vCPUs is the same whether you make a custom E2 with 8 vCPUs and 29 GB of memory, or use an e2-standard-8 which has the same 8 vCPUs and 32 GB). Memory is the same (your $1.34/GB/month for a 1-year commitment). Hope that makes sense. We'll try to improve the docs. Sorry. [1] https://cloud.google.com/blog/products/gcp/announcing-resource-based-pricing-for-google-compute-engine https://cloud.google.com/blog/products/gcp/announcing-resour... [2] https://cloud.google.com/compute/all-pricing#e2_machine-types https://cloud.google.com/compute/all-pricing#e2_machine-type...