[WORKFLOWS-394] Add TowerViewer roles ahead of sandbox deprecation
#125
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
thomasyu888
approved these changes
Aug 23, 2022
…/deprecate-sandbox-roles
|
I'm relying on the resource-based policies on the buckets to grant S3 access. So, these roles need to be in the same account as the bucket. Otherwise, you have need to set up cross-account access, which requires the IAM roles to gain S3 permissions, which gets complicated fast. |
BrunoGrandePhD
deleted the
bgrande/WORKFLOWS-394/deprecate-sandbox-roles
branch
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'm adding everyone's TowerViewer roles first to confirm that everyone can access their S3 buckets before removing their sandbox developer roles. I'll perform that step in a separate PR.