7 ms·
Stage 1: "Things are simple, our only secret is this AWS key, we don't need a secret manager." Stage 2: "For consistency, we'll handle our second and third sec
by michaelt 2y ago
Stage 1: "Things are simple, our only secret is this AWS key, we don't need a secret manager."
Stage 2: "For consistency, we'll handle our second and third secrets just like that first secret. Or handle them through our existing configuration management system, with just some minor tweaks."
Stage 3: "If we mess up the credentials for these edge devices, the software update, monitoring and remote management features will break and we'll have to recall the devices. We should be very cautious about making any changes."
Stage 4: "Even with a secret manager, we'd have to protect the credential used to access the secret manager. Not to mention a long-lived credential to bootstrap new devices, or re-image broken devices in the field. The real solution here is Secure Boot and credentials tied into the TPM. If we want to do this, we'll need a team of six full-time developers and our own custom linux distro"
Stage 5: "End-user features and business value are our priority right now, credential rotation is on the schedule for Q3 next year"
- fragmede 2y agoYet the "architect" arguing to use Kubernetes is the one making things more complicated and only doing it for their resume?
- 2muchcoffeeman 2y agoYou know what they say. Both can be true.