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
Failure connecting with IAM user #8034
Comments
Plus attach the file |
The complete cyberduck.log (testing with version 4.3.1 on Windows 7) contains only the following:
|
Here is a sample IAM policy to assist with your testing. Cyberduck on OSX works as expected based with this policy.
|
If the cause of the issue is the IAM policy, you should get the same results on both OS X and Windows. |
Since OS X works fine and Windows does not, I do not believe that the cause of the issue is the IAM policy. I documented the IAM policy here to assist with debugging. |
I have tried to replicate this issue with the same IAM policy and couldn't reproduce any connection failure running the current snapshot build on Windows. |
The upload with this policy to |
I tried the snapshot today, and it worked correctly. I did need to download the Microsoft Visual C++ 2010 Redistributable Package to get the snapshot to work, as I initially received a "msvcr100.dll is missing" error. |
For IAM policies restricting access to certain paths, the blog entry Grant access to user-specific folders in an Amazon S3 bucket is a good read. |
I have created an IAM profile for an S3 bucket and connected via Cyberduck on OS X, and all works fine there.
However when I attempt to connect via Cyberduck on Windows 7, I am unsuccessful in various ways with different versions:
In version 4.4.5, the software appears to hang upon a connection attempt
In version 4.4.4, the software connects but is not able to list the files/directories
In version 4.3.1, I am able to connect to the bucket and view the bucket/folder contents. I can retrieve files and delete files. However when I attempt to upload a file to a directory within the bucket where I know I have write permissions, I receive an "Access Denied" message.
I've confirmed that I am using the same credentials in the OS X version as the Windows version to make sure it is not an issue with my IAM policy.
The text was updated successfully, but these errors were encountered: