r/platform_engineering
Beyond Static Credentials: Reddit’s Journey to Workload Identity and mTLS
- upvotes
- 0
- comments
- 0
Post
Highlighted: the lines this signal was extracted from
Written by Pratik Lotia How we introduced automatically rotated workload credentials and migrated an existing service fleet to mutual TLS without a coordinated cutover. One Service, Several Sets Of Credentials Imagine building a new internal service. It calls another service, requires user context, reads from a database, requires access to a cloud resource and publishes events. Each dependency may have a different answer to the same question: how does the caller prove who it is and how do you manage access control? With static credentials, the answer usually involves provisioning a secret, deciding where to store it, granting access to the consumers of the secret, setting up authorization rules and wiring it into the application. Repeat that for every dependency and for every Kubernetes cluster or cloud environment it deploys to. The service is eventually ready to run, but its credentials still need coordination across multiple teams making it a high friction and time consuming process. When a security control is cumbersome enough, your customers will often find a way to bypass it or adopt less practices which leads to other issues such leaking credentials in code, sharing tokens and lack of regular rotation. We had accumulated versions of this problem across our infrastructure. Service authentication used static tokens. Database integrations had their own credential...
Keep reading with a free account
The rest of this post, and every signal for Reddit, is in your free account.
Also quoted as evidence
We chose SPIFFE as the identity standard and SPIRE as its implementation.
From the post
getting 90% of our in-cluster Go grpc traffic to use authenticated calls in the form of mutual TLS.
From the post