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

Cannot delete s3 object with custom sse encryption #1113

Closed
neelay-shah opened this issue Jun 2, 2017 · 4 comments
Closed

Cannot delete s3 object with custom sse encryption #1113

neelay-shah opened this issue Jun 2, 2017 · 4 comments
Assignees
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made. s3

Comments

@neelay-shah
Copy link

I am getting botocore.exceptions.ClientError: An error occurred (AccessDenied) when calling the DeleteObject operation: Access Denied error on s3.delete_object(Bucket=bucket, Key=source_file).

this can be due to existing issue on aws/aws-cli

Note: Permission for this operation is properly set and I can delete this object using
aws s3api delete-object --bucket {bucket_name} --key {object_path_for_file}.

@stealthycoin stealthycoin added the investigating This issue is being investigated and/or work is in progress to resolve the issue. label Jun 2, 2017
@stealthycoin
Copy link
Contributor

Hmmm thats super weird s3api delete-object would work and s3.delete_object wouldn't. They use the exact same logic in botocore under the hood to perform that API call.

@swetashre
Copy link
Contributor

swetashre commented Jan 15, 2020

@neelay-shah - Can you please let us know if you are still getting the error with latest version of boto3 and botocore ?

@swetashre swetashre added s3 closing-soon This issue will automatically close in 4 days unless further comments are made. and removed investigating This issue is being investigated and/or work is in progress to resolve the issue. labels Jan 15, 2020
@swetashre swetashre self-assigned this Jan 15, 2020
@no-response
Copy link

no-response bot commented Jan 23, 2020

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@no-response no-response bot closed this as completed Jan 23, 2020
@priyaljain03
Copy link

Hey @NigarumOvum , i too am facing same error while deploying , did you find the solution or what is wrong ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made. s3
Projects
None yet
Development

No branches or pull requests

4 participants