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 create a new S3 folder when S3 Server Side Encryption is required #10003

Closed
cyberduck opened this issue Jul 5, 2017 · 3 comments
Closed
Assignees
Labels
bug duplicate s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

a3439ce created the issue

  1. Set a bucket or IAM policy to require Server Side Encryption (http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html)
  2. In CyberDuck, Edit | Preferences | S3. For the Encryption option, ensure SSE-S3 (AES-256) is selected.
  3. Using CyberDuck, upload a file...success.
  4. Using CyberDuck, upload an empty folder...success.
  5. Using CyberDuck, File | New Folder. Give it a name (ex. "test"). Click Create...no success.

Error message: Upload test failed. Access Denied. Please contact your web hosting service provider for assistance.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Duplicate for #9378.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 7fea217.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug duplicate s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants