Clojurians Log v2

Looking at the peer deps, it looks like the memcache client uses it:

. com.datomic/memcache-asg-java-client 1.1.0.36
    . com.amazonaws/aws-java-sdk-ec2 1.11.22
      . com.amazonaws/aws-java-sdk-core 1.11.22

And I see these in the transactor distro:

aws-java-sdk-cloudwatch-1.12.564.jar
aws-java-sdk-cloudwatchmetrics-1.12.564.jar
aws-java-sdk-core-1.12.564.jar
aws-java-sdk-dynamodb-1.12.564.jar
aws-java-sdk-ec2-1.11.22.jar
aws-java-sdk-iam-1.12.564.jar
aws-java-sdk-kms-1.12.564.jar
aws-java-sdk-s3-1.12.564.jar
aws-java-sdk-sns-1.12.564.jar
aws-java-sdk-sqs-1.12.564.jar
aws-java-sdk-ssm-1.12.564.jar

We have an engineer dedicated to upgrading this and they are actively working on it

Awesome, thanks Joe!

So looking forward to SSO support!

It's possible this is already happening but I'll mention it since there's some work underway here. Could you consider supporting user-supplied credential providers instead of basing everything on the URI / environment properties? I asked about this a while ago: https://clojurians.slack.com/archives/C03RZMDSH/p1723472901947619

The current provider (despite its deficiencies) is based on the Java SDK v1 interfaces. I've written a custom credentials provider that wires in SSO support (using the credentials left laying around by the AWS SSO CLI) and it works. My point is that it is already possible to create user-controlled credentials. The Datomic Cloud client has an option just for this. It just dawned on me that maybe you were referring to the on-prem version and maybe it doesn't have that hook....

Yeah, I'm using Datomic Pro peer library and there is no public API for a user-supplied credential provider. We monkey patched support for it but would prefer to not have to do that 🙂