Add placeholder file for AWS credentials environment variables #23
Conversation
This file contains hidden or 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
…ther env variables
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
With the new
grantedbased approach to managing our AWS credentials, we can't rely on the hardcoded default AWS credentials when using MWAA local runner. Instead, we need to assume our role, export its temporary credentials to env variables, copy these variables to a file, and load that file when starting the MWAA local runner.This PR simply adds the placeholder file to receive the environment variable. It's a different file from the existing
.env.localrunnerso that it can be overwritten every time we launch the MWAA localrunner without overwritting other variables in.env.localrunner.This is a companion pull request to https://github.com/alan-eu/alan-jobs/pull/11072