Also add support for SSM secrets in AWS TriggerAuthentication

[sneljo1]

Proposal

Besides accessing secrets from secretsmanager, similar to secrets-store-csi-driver-provider-aws, we should be able to fetch secure secrets from SSM. This will allow more flexibility for implementation

Use-Case

This will allow users already using SSM to not have to copy their secrets

Is this a feature you are interested in implementing yourself?

No

Anything else?

No response

[JorTurFer]

Hello
I'm not sure if I get your point totally. Does SSM mean AWS Systems Manager? Assuming that yes, I think that we can extend the current implementation of the AWS Secret Manager and support calling to the new service (with another parameter to declare it).
WDYT @kedacore/keda-contributors ?

[sneljo1]

I'm not sure if I get your point totally. Does SSM mean AWS Systems Manager? Assuming that yes, I think that we can extend the current implementation of the AWS Secret Manager and support calling to the new service (with another parameter to declare it).
WDYT @kedacore/keda-contributors ?

Yes indeed, in Parameter Store you can also store secure secrets. The secrets-store implementation uses for example a objectType property for each secret to differentiate between using secretsmanager or ssmparameter. But i've seen other implementations that make the distinction by taking into account a ssm: prefix to decide to retrieve it from Parameter Store instead.