vadimska

If you are building billing integrations for FinOps or CloudOps, I have bad news: the data you just fetched from that SaaS API is probably wrong.

What can be a potential use case for something like this?

I hate hand-tagging my cloud resources.

I think egress costs are the primary factor behind "cloud bill shock". Tracking and understanding them is a key to avoid surprises when you get your monthly invoice from cloud provider.

My thoughts exactly. I am now working on this problem myself and I will share my results soon.

This probably will depend on CDN. Google's CDN is part of the Load Balancer itself and therefore it won't affect geolocation. With "3rd party" CDNs it's different, of course.

Finally, the free version of MaxMind is great. Thanks for mentioning it.

It would be pretty easy to build. Probably something you can do end-to-end in one or two days.

Check this out: https://twitter.com/jasoncartwright/status/98882315371465113...

yep. also, spares some compute cycles for your app

Well, I am sure MaxMind provides a lot of value for many use-cases. However, I just need something very basic (country, city, lat and long) and getting this "out of the box" from Google's LB is blessing for me.

Live Migration is such an awesome feature on Google Cloud. Instead of getting emails saying "your instance is running on degraded hardware, please reboot", your instance is just automagically being migrated to another physical machine with almost no impact on your workload.

I have used the CLI and the quotes worked fine for me. Here is the complete command I have used:

gcloud beta compute backend-services update app --custom-request-header 'X-Client-Geo-Location:{client_region},{client_region_subdivision},{client_city}' --custom-request-header 'X-Client-Geo-Region:{client_region_subdivision}' --custom-request-header 'X-Client-Geo-LatLong:{client_city_lat_long}' --custom-request-header 'X-Client-TLS-Version:{tls_version}' --custom-request-header 'X-Client-TLS-Chiper:{tls_cipher_suite}' --custom-request-header 'X-Client-Hostname:{tls_sni_hostname}' --custom-request-header 'X-Client-RTT:{client_rtt_msec}'

Not everything goes thru CloudFront. I hope ELB/ALB will have this feature soon too!

Exactly! I was using GAE for 9 years now and it's so easy to have these headers automagically being attached to your requests. Finally, Google Compute Engine has the same convenient way of geolocating requests.

Thanks, Aviv! That's really useful.

Who thought people are buying so much weed ;-)

+1 ;-)