Posts

Don’t Just say Hello # I’ve had a few messages at ${WORK} lately which simply start with a: “Hello” followed by nothing. Sometimes there’s an ask of how a thing, typically a weekend, was.

When I’ve finished using a hard disk for a customer project I’ll erase the data on it so the drive can be reused without the customers data getting exposed. A simple reformat of the disk would cover most scenarios but there’s a chance data can still be recovered after this so I need to be sure its not recoverable. The Secure erase feature of the disk would be perfect for this, or so I thought.

I have a need to block a large list of ever changing IP addresses from servers and systems I operate.

Following on from my previous post: Packer: Building images on Google Cloud You should now be able to build compute images on GCP and you may have used this to build a pre-configured image you can effortlessly deploy again and again without having to wait to install software.

We can use IAM to control who has access to what within our project and who can do what to things like storage buckets, but what if we wanted to restrict when someone could do something or to what object in a bucket. That’s where IAM Conditions come in to play.