-
Notifications
You must be signed in to change notification settings - Fork 67
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
Support getting VEDA S3 buckets being properly accessed from VEDA hubs #4535
Comments
@yuvipanda the PR is ready. Note: after we test this out on staging, and confirm we're happy with all the permissions on both side we'll be doing a second PR to allow this bucket on additional NASA VEDA related hubs. |
Great, @wildintellect. Please tag @sgibson91 in PRs so she gets notified, and she'll merge them. Note she's in the UK timezone so that may affect when these happen. |
Waiting for external input from the community. |
Sarah did this with #4609 |
I tested out the veda s3 bucket access in production and and I'm able to get access now. Thanks |
As part of NASA-IMPACT/veda-jupyterhub#53, we need to merge and
terraform apply
some PRs like #4533.This is part of https://github.com/2i2c-org/meta/issues/1368.
The VEDA team will make appropriate PRs (like #4533), but currently it requires someone from 2i2c engineering to apply them
This issue is to track (on behalf of 2i2c engineering) providing support for reviewing and merging these PRs
Definition of done
The text was updated successfully, but these errors were encountered: