-
Notifications
You must be signed in to change notification settings - Fork 8
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
Permission errors when accessing output files in S3 #1580
Comments
To add some context, for https://hyp3-api.asf.alaska.edu, we hope to enable S3 access again and we're looking into options which is why* we haven't removed the s3 info for the files. We'll either need a policy change on the NASA side or to stand up an application to grant S3 credentials. That said, it's been 10 months already, and it's unlikely to change in the foreseeable future. *We also have "custom" hyp3 deployments outside of NASA's managed AWS environment that do have fully public buckets and can utilize the s3 keys. |
Hi ASF team, I hope you are well. I was wondering if you got to addressing this issue pls? Thank you for considering my questions. Greetings from hot and humid NC. Regards, Mark |
pls also respond to [email protected] thank you, Mark |
Hi ASF team, I am now using the urls for download to s3. Am running parallel lambdas and it works but I think copying keys from s3 to s3 would be faster as I am in US-west2. Pls let me know when you get allowing copying of S3 keys again so I can modify my code. Tnx, Mark |
@markbroich getting direct s3 access is a significant effort and we do not currently have a timeline for doing so. We'll update this issue if and when we provide it. |
Jira: https://asfdaac.atlassian.net/browse/TOOL-2040
Completed HyP3 jobs include an AWS S3 Bucket and Key for their output files, but attempting to access those files using the AWS CLI or the boto3 python library results in
AccessDenied
orForbidden
errors. For example:Accessing these files directly in S3 was possible until Jun 2022, when the https://hyp3-api.asf.alaska.edu/ API was migrated to a NASA-managed AWS platform where security controls prevent direct public access to files in S3. The bucket and key are still included in the description of each output file, but attempts to use boto3 or the AWS CLI now fail with permissions errors.
The text was updated successfully, but these errors were encountered: