Use a new S3 bucket instead of mciuploads#900
Merged
Conversation
This was referenced Feb 27, 2026
Collaborator
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
autarch
force-pushed
the
02-27-use_a_new_s3_bucket_instead_of_mciuploads_
branch
3 times, most recently
from
86040a7 to
86ca04c
Compare
tdq45gj
reviewed
Feb 27, 2026
| bucket: mciuploads | ||
| permissions: public-read | ||
| bucket: evergreen-project-mongo-tools-i6qg5nn6nbm | ||
| permissions: private |
Contributor
There was a problem hiding this comment.
Will the uploaded file be available for download from Evergreen UI?
Contributor
There was a problem hiding this comment.
Seems that the default visibility is "public" according to the doc, so it should be good.
Collaborator
Author
There was a problem hiding this comment.
Actually, I needed to add visibility: signed to make this work. The links showed up in Evergreen, but they resulted in permissions error without setting visibility.
tdq45gj
approved these changes
Feb 27, 2026
| bucket: mciuploads | ||
| permissions: public-read | ||
| bucket: evergreen-project-mongo-tools-i6qg5nn6nbm | ||
| permissions: private |
Contributor
There was a problem hiding this comment.
Seems that the default visibility is "public" according to the doc, so it should be good.
autarch
force-pushed
the
02-27-use_a_new_s3_bucket_instead_of_mciuploads_
branch
2 times, most recently
from
2f6832c to
b61ba1d
Compare
Collaborator
Author
autarch
changed the base branch from
02-25-tools-4102_add_a_mise.toml_with_all_of_our_tools
to
graphite-base/900
This is being done for two reasons. First, we want to move projects away from all using the shared `mciuploads` bucket. Second, the credentials to access `mciuploads` are only available for the DB Tools Evergreen project for the `master` branch. When we make a PR off a different branch, we cannot see those credentials. That means those branches cannot interact with S3 in CI, which leads to lots of CI failures. Switching to a new bucket and using `ec2.assume_role` to access that bucket means this works on any branch.
autarch
force-pushed
the
02-27-use_a_new_s3_bucket_instead_of_mciuploads_
branch
from
b61ba1d to
d4e8fa0
Compare
autarch
added a commit
that referenced
this pull request
Mar 2, 2026
This reverts commit 5745e79. I realized that this may break the release process. It's not clear to me that using this new bucket will work for that case. We don't have any good way to test the release process, so I'll just revert this for now.
autarch
added a commit
that referenced
this pull request
Mar 3, 2026
This reverts commit 5745e79. I realized that this may break the release process. It's not clear to me that using this new bucket will work for that case. We don't have any good way to test the release process, so I'll just revert this for now.
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.
This is being done for two reasons.
First, we want to move projects away from all using the shared
mciuploadsbucket.Second, the credentials to access
mciuploadsare only available for the DB Tools Evergreen project for themasterbranch. When we make a PR off a different branch, we cannot see those credentials. That means those branches cannot interact with S3 in CI, which leads to lots of CI failures. Switching to a new bucket and usingrole_arnto access that bucket means this works on any branch.This also changes all our S3 uploads to be private, but I don't think there was any reason for these to be publicly readable. People outside MongoDB can't see Evergreen logs, so they'd have no way to find the relevant URLs anyway.