Alexandre Dutra

> Will this work for eks IRSA/Pod Idendity? @dorsegal I can't tell for sure I'm afraid, but it seems so: IRSA uses `WebIdentityTokenFileCredentialsProvider` according to this SO question: https://stackoverflow.com/questions/70964807/aws-java-sdk-v2-not-using-irsa-iam-role-in-eks And...

Side note: GKE clusters have a similar way of binding roles to service accounts. Whatever solution we come up with here needs to be applied to GCS options as well....

> > Actually, we could introduce a similar mechanism like auth-type (`GcsBucketOptions.GcsAuthType`) to S3 and users can configure it explicitly to `WORKLOAD_IDENTITY`. WDYT? > > @adutra ^ As Olivier said,...

> The difference is that you explicitly tell Nessie to do it, so if you configure it explicitly, you have to live with the fact :) Hm if people configure...

Switching to draft because I think we need to discuss the design.

Supporting other providers is not a problem imho, I basically copied everything from Quarkiverse. Other providers could be useful for users that know which type of authentication they want, as...

As requested, I simplified the design to just 2 modes: default and static.

@sdasdasd1 this might not solve your problem but I noticed that your env vars have odd names, e.g. `NESSIE_CATALOG_SERVICE_S3_ACCESS-KEY_NAME` – note the dash. It should be imho `NESSIE_CATALOG_SERVICE_S3_ACCESS_KEY_NAME`.

@sdasdasd1 this might not solve your problem but I noticed that your env vars have odd names, e.g. `NESSIE_CATALOG_SERVICE_S3_ACCESS-KEY_NAME` – note the dash. It should be imho `NESSIE_CATALOG_SERVICE_S3_ACCESS_KEY_NAME`.

Check the conversion rules here: https://smallrye.io/smallrye-config/Main/config/environment-variables/