aws/aws-secretsmanager-jdbc

Support providing regions/endpoint configuration at connection-time

steve-thousand opened this issue · 2 comments

steve-thousand commented

Currrently, configuration of the secrets manager region and endpoint needs to be done through system properties and environment variables. There are a few problems with this approach that I have run into:

  1. If ARNs ever have to be retrieved from different regions, the driver only supports one
  2. Setting the environment variables has been an issue in some environments, like when EMR runs your code in yarn containers

If region/endpoint could be provided as connection properties, the region/endpoint could be used dynamically.

jbct commented

Hi steve-thousand. Could you speak a bit more to your use case? What are you looking to have happen?