The cloud role that outlived its project

Portrait of Jun Tanaka, a man in his thirties in glasses, lit by a dark terminal

Build pipelines collect permissions over time. Each project adds a little, and nobody takes it back when the project ends.

On one sample cloud test, a single build role could read every customer’s storage. It had been granted that for a migration three years earlier.

A short review

  • List every role a pipeline can use.
  • Pull ninety days of usage from the cloud provider.
  • Remove anything that was not used.
  • Give each remaining role a named owner and an end date.

A permission with no owner is a door with no one responsible for the lock.

Keep it small

Do this once for the riskiest pipeline, then put the end date in the template so new roles expire by default. It takes an afternoon, and it removes most of what we would otherwise find.

About the author

Jun leads cloud testing at Wardline and follows identity paths until one ends somewhere it should not. Fictional author, demo content.

Related field notes