Support AWS Lambda #415
Merged
Support AWS Lambda #415
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
(JFYI) When AWS API runs without AWS_SESSION_TOEKN, it threw an error message |
|
@umihico Hi there! Can you please rebase your branch? Thank you! |
umihico
force-pushed
the
fix/aws-session-token
branch
from
56a1d5c
to
4c0534e
Compare
|
@n-rodriguez |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I tried to use on AWS Lambda and needed to patch a little bit. Instead of fetching metadata like EC2 or ECS, AWS Lambda initially has
AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEYandAWS_SESSION_TOKENfrom the beginning, as reserved environment variables. In this case, we need to pass these variables directly into fog orAws::S3::Resource.