Explore using onetimesecret.com (or a self-hosted version) to pass secrets to user-data #11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Doing this would allow passing a token that explodes on use - so it would only be available during provisioning.
Interesting idea - but that does then make re-provisioning something you can't do in a hurry, because the secrets-would have to be preloaded .. presumably by hand?
I suppose one could store a batch of a longer-lived credentials encrypted with one single-use key, to be retrieved this way? Maybe combine with https://github.com/getsops/sops ?
I've not used sops, though it's got a huge readme. This may be good or bad :)
Thinking about it more, perhaps the best way is some kind of bootstrap cred that gives access to whatever. The cred itself could be longer-lived too - it would just be access that's one time. Once the box has built it should in theory already be trusted to get secrets via some other mechanism?