You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
AWS has released pod-level permissions a few months ago, allowing Vault to be run in EKS without having to give all the neighboring pods the same permissions to the AWS APIs being used.
This feature is support for SDK versions > 1.23.13 (as described here)
The version currently used in Vault is 1.19, and so this cannot be used.
Describe the solution you'd like
Update the AWS SDK to the latest v1 version, or at least version 1.24
Describe alternatives you've considered
There are two alternatives to this, both are not ideal:
Providing an access key and a secret key, either via the values.yml (bad practice) or via a mounted Secret
Assigning a role to all the worker nodes, giving all the pods in the cluster access to the resources used by Vault for storage and encryption
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
AWS has released pod-level permissions a few months ago, allowing Vault to be run in EKS without having to give all the neighboring pods the same permissions to the AWS APIs being used.
This feature is support for SDK versions > 1.23.13 (as described here)
The version currently used in Vault is 1.19, and so this cannot be used.
Describe the solution you'd like
Update the AWS SDK to the latest v1 version, or at least version 1.24
Describe alternatives you've considered
There are two alternatives to this, both are not ideal:
Secret
The text was updated successfully, but these errors were encountered: