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
We have a secret value we share with all AWS accounts via Resource Access Manager. I would like to leverage Secrets Store CSI Driver and this provider to mount the secret to a workload that relies on the value. However, this is currently not possible with the provider. The documentation states: For SSM Parameter Store, this must be the Name of the parameter and can not be a full ARN.
Because I am hard-headed, I tried anyway just to see what would happen. This results in an error which seems to occur because the name used to fetch the parameter does not match the name returned in the response. Stack trace include below.
This limitation makes it so we cannot use SSM Parameters shared via AWS RAM.
Looking at the lines where error gets thrown, you can see it uses Name from the response. When trying to supply this to the batchDesc map, it results in a nil descriptor since the key should be the ARN of the parameter.
Describe the bug
Hey folks!
We have a secret value we share with all AWS accounts via Resource Access Manager. I would like to leverage Secrets Store CSI Driver and this provider to mount the secret to a workload that relies on the value. However, this is currently not possible with the provider. The documentation states:
For SSM Parameter Store, this must be the Name of the parameter and can not be a full ARN.
Because I am hard-headed, I tried anyway just to see what would happen. This results in an error which seems to occur because the name used to fetch the parameter does not match the name returned in the response. Stack trace include below.
This limitation makes it so we cannot use SSM Parameters shared via AWS RAM.
Error On Mount:
To Reproduce
Steps to reproduce the behavior:
objectName
of one of the objects.Do you also notice this bug when using a different secrets store provider (Vault/Azure/GCP...)? No
Expected behavior
ASCP should be able to handle AWS RAM-shared SSM parameters.
Environment:
EKS 1.29
Additional context
RAM-shared SSM paremeter:
arn:aws:us-east-1:123456789012:ssm:parameter/foo/bar
SecretProviderClass:
GetParametersResponse:
Looking at the lines where error gets thrown, you can see it uses
Name
from the response. When trying to supply this to thebatchDesc
map, it results in anil
descriptor since the key should be the ARN of the parameter.secrets-store-csi-driver-provider-aws/provider/parameter_store_provider.go
Lines 137 to 158 in eec8172
It seems that this issue could be solved by checking if
descriptor
isnil
after 153, and if so, trying to use the ARN instead as the key.The text was updated successfully, but these errors were encountered: