use recent AWS CLI version #14
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 propose to use a newer version of the AWS CLI for writing the S3 backups.
When running Kubernetes with AWS EKS, there is a standard way of mapping Kubernetes service accounts to AWS roles:
https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html
Unfortunately, this depends on having a more recent version of the CLI, the currently installed version 1.16 (via apt and debian:buster) does not work for me.
The fix is to install a current version via pip3.