MONGOCRYPT-838 use S3 role for s3.put#1116
Closed
kevinAlbs wants to merge 1 commit intomongodb:masterfrom
Closed
Conversation
Contributor
|
These changes are probably subsumed by #1117 |
Contributor
Author
Agreed. Closing. |
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
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.
Use an S3 role for the
s3.putcommands. This is intended to ease switching between S3 roles in a step towards resolve MONGOCRYPT-838.The Evergreen repo config is updated to add role variables:
role_arn_for_mciuploads.role_arn_for_release.These values are also added to AWS Secrets Manager under
drivers/libmongocryptas a backup.