Allow adding any arbitrary AWS Secrets Manager secrets

[tvrmsmith]

It would be great if we could add additional AWS Secrets Manager secrets as property sources. Currently, I'd like to use the RDS secrets feature as well as other secrets, but the current way of adding secrets makes it difficult to do this.

It could be configured something like:

aws:
  secretsmanager:
    additional-secrets:
      - /secret/secret1
      - /secret/secret2

[maciejwalkowiak]

@tvrmsmith just so that I understand it correctly - these additional secrets would contains raw values and everything after prefix (/secret/) would be a property name?

[eddumelendez]

I think this link can be useful to understand the proposal. @tvrmsmith is what you meant?

[maciejwalkowiak]

In case of RDS password I would like us to use this library in 3.0 https://github.com/aws/aws-secretsmanager-jdbc. I have it working in the prototype (... and made video about it how to use this library ;-) https://www.youtube.com/watch?v=gIbr6-AR6T8)

[nhomble]

Instead of an array of strings, maybe we should be a little more flexible and allow users to configure the desired name as well? I think we're going to hit a wall if we only depend on the library to interpret the secret name from the path. Maybe like

aws:
  secretsmanager:
    additional-secrets:
      secret1:
        path: /secret/secret1
      different.name:
        path: /secret/secret2

and then I would be able to pull the secret from Environment with .getProperty("secret1") or .getProperty("different.name")

[nickcaballero]

Agreed with @nhomble. I have a similar implementation of this via a PropertyResolver.