-
Notifications
You must be signed in to change notification settings - Fork 32
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
Setup - Need S3 object read permission #1
Comments
Can you try running |
Yes, certainly i am able to list the object and infact many other objects
under that hierarchy. But the copy doesn't work. I checked with AWS support
and they confirmed that the owner object permission is not properly set for
it to be copied. Let me know if you have any questions.
Thanks
Mahaboob Vali Shaik
…On Thu, Dec 7, 2017 at 2:36 PM, Venkata krishnan Sowrirajan < ***@***.***> wrote:
Can you try running aws s3 ls s3://public-qubole/lambda/
spark-2.1.0-bin-spark-lambda-2.1.0.tgz? I tried with a different set of
keys and the copy worked.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMmZZJm7aWczsoz4OVv2hUA3xUAXamKOks5s-D4lgaJpZM4Q55fM>
.
|
Alright, that was an issue from our side, the keys owner didn't allow public to do GET operation. I think now it should be fine, we changed the owner permissions. Can you please try again and let us know if that fixes the issue? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per instructions, I was trying to copy the file and errors out.
aws s3 cp s3://public-qubole/lambda/spark-2.1.0-bin-spark-lambda-2.1.0.tgz s3://myBucket-xxx/spark-on-lambda/spark-2.1.0-bin-spark-lambda-2.1.0.tgz --acl bucket-owner-full-control
Error:
fatal error: An error occurred (403) when calling the HeadObject operation: Forbidden
Could you provide appropriate access for the users to access the neccesary files.
Thanks
Vali
The text was updated successfully, but these errors were encountered: