Blog

Cloud notes.

The paths we keep seeing, how they work and how to close them. Written by the engineers behind the map.

One new note a month

Engineer walking two colleagues through a magenta path on a wall graph

Why we count hops, not settings

A list of 12,406 grants tells you little. How a count of hops shows which three to fix first.
Read the note
Engineer's hands at a keyboard in front of a dark identity graph, a hardware security key on the desk

Three questions for any long-lived access key

Who holds it, what can it reach, and when did it last run? A short review that retires most old keys.
Read the note
Minh Tran, build log lines reflected in his glasses in low magenta light

What a deploy token can reach on a bad day

Most short paths to production start in a build. How to find out what yours can really touch.
Read the note
Engineer's hand on a laptop in front of a log console with two lines highlighted in magenta

Public buckets are the easy part

The buckets that cause real trouble are private. They are just readable by far too many roles.
Read the note
Arjun Nair working at a laptop and a portable dark monitor showing a graph with one magenta path

Fixes as pull requests, not tickets

A ticket asks someone to work out the fix. A small Terraform change only needs a review.
Read the note
Two engineers at a row of dark monitors showing network graphs, one pointing at a screen

Reading a trust policy in five minutes

Trust policies decide who can become a role. Four lines tell you most of what you need.
Read the note
1 2
Monthly cloud notes

One short email.

A path we keep seeing and how to close it. No sales mail.