You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The error is: "Upload FileName failed. Access Denied, Please contact your web hosting service provider for assistance."
It is odd that the error is Upload failed, while I am attempting to delete a file from S3. If I hit refresh after receiving the error, the file is gone, so the file delete operation is successful, and the error is occuring after the delete.
This error does not occur when using an IAM user with full S3 access. The error only happens using IAM users that are restricted to a particular bucket. I have an IAM policy set up to allow GET/PUT/DELETE object access to a specific bucket, and the error only occurs when logged into S3 via Cyberduck using a user with that IAM policy. Looking at the Log Drawer below, it looks like the first request to S3 is a DELETE, which appears to work just fine. After the delete, a GET is requested which receives a 403 forbidden response.
The error is: "Upload FileName failed. Access Denied, Please contact your web hosting service provider for assistance."
It is odd that the error is Upload failed, while I am attempting to delete a file from S3. If I hit refresh after receiving the error, the file is gone, so the file delete operation is successful, and the error is occuring after the delete.
This error does not occur when using an IAM user with full S3 access. The error only happens using IAM users that are restricted to a particular bucket. I have an IAM policy set up to allow GET/PUT/DELETE object access to a specific bucket, and the error only occurs when logged into S3 via Cyberduck using a user with that IAM policy. Looking at the Log Drawer below, it looks like the first request to S3 is a DELETE, which appears to work just fine. After the delete, a GET is requested which receives a 403 forbidden response.
The text was updated successfully, but these errors were encountered: