Enable IAM role-based auth between EC2 and S3 #99
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
related to alephdata/aleph#3185
What
Enables IAM role-based auth by allowing environment variables
AWS_KEY_ID
andAWS_SECRET_KEY
to be left unpopulated. When neither is populated,key_id
andsecret_key
won't be passed to the s3 client constructor which will instead look for credentials in instance metadata.Why
As described in the issue above, role based auth has a few advantages over user-based auth:
Note: when Aleph is running on docker on an EC2 instance, it might be necessary to increase its launch template's HttpPutResponseHopLimit from the default of 1 to 2 so that instance metadata can be fetched.