aws hubs: consistent setup of cloud permissions and bucket envs #3977
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 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.
singleuser.cloudMetadata.blockWithIptables
defaulting to false, for example for opensci's staging hub.