Skip to content

use aws default credential provider if no access keys provided#39

Merged
jaredstehler merged 1 commit intomasterfrom
js-default-aws-creds
Nov 5, 2024
Merged

use aws default credential provider if no access keys provided#39
jaredstehler merged 1 commit intomasterfrom
js-default-aws-creds

Conversation

@jaredstehler
Copy link
Copy Markdown
Contributor

Uses the default credentials provider when no s3 access key or secret are provided in configuration:

AWS credentials provider chain that looks for credentials in this order:

  1. Java System Properties - aws.accessKeyId and aws.secretAccessKey
  2. Environment Variables - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
  3. Web Identity Token credentials from system properties or environment variables
  4. Credential profiles file at the default location (~/.aws/ credentials) shared by all AWS SDKs and the AWS CLI
  5. Credentials delivered through the Amazon EC2 container service if AWS_CONTAINER_CREDENTIALS_RELATIVE_URI environment variable is set and security manager has permission to access the variable,
  6. Instance profile credentials delivered through the Amazon EC2 metadata service

Adapted from #23

@jaredstehler jaredstehler merged commit 1b8aae8 into master Nov 5, 2024
@jaredstehler jaredstehler deleted the js-default-aws-creds branch November 5, 2024 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant