[config]: Add encryption configuration#238
Open
pseudomuto wants to merge 1 commit into
Open
Conversation
Adds an Encryption section to S2SProxyConfig so the proxy can be configured with KMS-backed key material for payload encryption. The config defines the active KMS key URI, any retired URIs that may still be needed for decryption after a provider migration or key rotation, and the DEK validity/renewal durations that drive rotation behavior. Key URIs follow the [gocloud.dev/secrets] URL scheme so we can transparently support GCP KMS, AWS KMS, and Azure Key Vault without provider-specific config branches. A testing scheme is also accepted for local development and tests where standing up a real KMS isn't practical. Validation happens at YAML unmarshal time so misconfigured URIs fail fast at startup rather than surfacing later when encryption is first exercised. [gocloud.dev/secrets]: https://gocloud.dev/howto/secrets/
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an Encryption section to S2SProxyConfig so the proxy can be configured with KMS-backed key material for payload encryption. The config defines the active KMS key URI, any retired URIs that may still be needed for decryption after a provider migration or key rotation, and the DEK validity/renewal durations that drive rotation behavior.
Key URIs follow the gocloud.dev/secrets URL scheme so we can transparently support GCP KMS, AWS KMS, and Azure Key Vault without provider-specific config branches. A testing scheme is also accepted for local development and tests where standing up a real KMS isn't practical.
Validation happens at YAML unmarshal time so misconfigured URIs fail fast at startup rather than surfacing later when encryption is first exercised.