I am evaluating CrushFTP for our business. What I am trying to accomplish is to setup CrushFTP with a S3 as our file storage.
So the first thing I did is to create a user (test_user). Still in the VFS tab, I clicked on the "Create Remote Item" button. I selected S3 as the FIle Type.
I entered a name for the new VFS Item (TestS3). I added "FTP-Service/" to the end of the URL.
I entered my Access Key and Security Key (which I have used via another client, so I know it works).
So the URL looks like this: s3://removed:firstname.lastname@example.org/FTP-Service/
I clicked OK, then Save All Changes.
What I expect to happen (which doesn't) is when I double click on the TestS3 folder, I should see another folder (called US; previously setup via AWS Console). But I do not see the US folder. Within the US folder, I have 1 CSV file. But I don't get that far.
spinkb @ Fri Feb 14 14:26:19 EET 2014 Go to your about tab, click update now.
You will get a newer build that should fix this issue. If not, let me know again the debug level 2 log data like you just did.
about 3 years ago
codewzrd @ Fri Feb 14 15:34:46 EET 2014 So the fix helped me. It showed me the error I was getting. [color=red]S3Client:PROXY: AccessDeniedAccess Denied21EF9C23E391C0D2PbQ1FIjt/N/2JQh6xsNB6rSKcupoPGOWp3q+iVIlmtuEJSQr1P+kuHBMF/TemCG1 [/color]
I don't know why I was getting that error message against the FTP-Service bucket. So I deleted the bucket. I created a new bucket and tried again and it worked this time.
I am not sure why I could not access the bucket as I could from my custom .NET client. Anyway, S3 folder names are [b]case sensitive.[/b]
about 3 years ago
spinkb @ Fri Feb 14 15:46:02 EET 2014 There is a known, impossible to solve bug related to mixed case bucket names. The S3 documentation does not explain how to correct this, and we have spent hours trying to debug what it expected to no avail.
We will not use the S3 libraries as they are a *HUGE* bloat for the protocol that we need to do, and cannot do the advanced things we need as well.
So we are stuck with not being able to access a S3 bucket if it has mixed case.