-
Notifications
You must be signed in to change notification settings - Fork 485
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor S3 credential provisioning #5733
Comments
This was referenced Apr 9, 2019
poikilotherm
changed the title
Refactor S3 driver options and credential provisioning
Refactor S3 credential provisioning
Dec 16, 2021
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Dec 16, 2021
This change does not alter existing behaviour. Anyway with current or future use of the ~/.aws profiles/credentials may continue to do so. This is useful to serve traditional installations, testing with AWS CLI etc. Containerized installations profit from not having to generate the AWS CLI specific files. Also testing gets easier by providing credentials via env or system props.
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Dec 16, 2021
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Dec 16, 2021
Merged
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Dec 16, 2021
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Dec 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #5478 the configuration of Swift storage is pretty much streamlined to contain endpoint(s), access credentials and others in JVM options. This is very usefull when configuring for usage on K8s and similar.
Currently, a S3 storage endpoint can be configured via JVM options. For credentials, you need to create
~/.aws/credentials
. (see http://guides.dataverse.org/en/4.12/installation/config.html#manually-set-up-credentials-file)The code in
S3AccessIO.java
should be refactored to use a credentials provider chain to read from AWS profile files or retrieve secrets via MicroProfile Config API.The text was updated successfully, but these errors were encountered: