Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws hubs: consistent setup of cloud permissions and bucket envs #3977

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

consideRatio
Copy link
Member

@consideRatio consideRatio commented Apr 22, 2024

I saw that we had several hubs where buckets were setup in terraform, but not made available to hubs. This PR setups access to the buckets.

Does parts of whats needed for #3864 - looked at all AWS clusters' hubs.

  • This PR hasn't verified access works, and for several hubs I think it won't work due to singleuser.cloudMetadata.blockWithIptables defaulting to false, for example for opensci's staging hub.
  • This PR has used terraform as the source of truth if hubs should have access to buckets - so if a scratch bucket was defined for staging, then staging should have access to if for example. So, we could opt to instead delete the buckets from terraform as an alternative to setting up access to it.

This comment was marked as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant