dimas-b opened a new issue, #3338: URL: https://github.com/apache/polaris/issues/3338
### Is your feature request related to a problem? Please describe. Currently (discussed under #3330) Polaris supports the "current" KMS keys ARN and a list of "allowed" keys ARNs. The same encrypt / decrypt access is granted to all of those ARNs in vended credential policies (STS session policies). However, historical keys do not need the "encrypt" permission. Polaris and its clients normally need only the "decrypt" permission to read older data files. ### Describe the solution you'd like * Add new storage config property: `legacy-kms-keys` * Grant only "decrypt" access to `legacy-kms-keys` * Grant both "decrypt" and "encrypt" access to `allowed-kms-keys` (current behaviour) * Deprecate the `current-kms-key` property (forward existing values to `allowed-kms-keys`) During manual KMS key rotation, the admin user will add all keys that may be used for encryption to `allowed-kms-keys`. Then, the admin user will adjust AWS configuration, then move the decommissioned KMS key to the `legacy-kms-keys` list. ### Describe alternatives you've considered _No response_ ### Additional context _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
