The issue here is that s3curl has a list of valid "endpoints" it uses to help it compute the canonicalized path. You can see at the end of the StringToSign there's "/localhost/". This is incorrect.
The fix is to configure s3curl to include your endpoint (e.g. localhost). The instructions are in the ECS documentation (see step 4 under this topic):
OK, adding @endpoints to .s3curl fixes the issue when running s3curl on the local machine - which is really not useful for something else than testing.
We still have an issue with "external" Hosts trying to access ECS using the "S3-protokoll" like S3-Browser and EMC CloudArray.
So, I've solved the issue with the S*-Browser as well - I have to use the SSL-port (9021) instead of 9020.
Now I have run into another problem...
In the S3-Browser I can upload a file to a Bucket (and I can see on the Dashboard that the file is uploaded as "Used Data" increases with exactly the filesize) but when the S3-Browser tries to list the content of the Bucket I get an error "Internal error".
benschumacher
1 Rookie
•
75 Posts
0
April 26th, 2016 12:00
Have you tried running your first example using 127.0.0.1:9020 instead of localhost:9020?
-Ben
JasonCwik
281 Posts
0
April 26th, 2016 14:00
The issue here is that s3curl has a list of valid "endpoints" it uses to help it compute the canonicalized path. You can see at the end of the StringToSign there's "/localhost/". This is incorrect.
The fix is to configure s3curl to include your endpoint (e.g. localhost). The instructions are in the ECS documentation (see step 4 under this topic):
http://www.emc.com/techpubs/ecs/ecs_create_bucket-2.htm?_ga=1.42639269.1631791353.1456427359#GUID-2E37CDB4-12FB-4BA7-937…
This issue is specific to how s3curl works and is not a general ECS issue.
DMJO
14 Posts
0
April 26th, 2016 23:00
This results in the same issue as with localhost.
--
D/\N
DMJO
14 Posts
0
April 26th, 2016 23:00
OK, adding @endpoints to .s3curl fixes the issue when running s3curl on the local machine - which is really not useful for something else than testing.
We still have an issue with "external" Hosts trying to access ECS using the "S3-protokoll" like S3-Browser and EMC CloudArray.
D/\N
DMJO
14 Posts
0
April 27th, 2016 02:00
So, I've solved the issue with the S*-Browser as well - I have to use the SSL-port (9021) instead of 9020.
Now I have run into another problem...
In the S3-Browser I can upload a file to a Bucket (and I can see on the Dashboard that the file is uploaded as "Used Data" increases with exactly the filesize) but when the S3-Browser tries to list the content of the Bucket I get an error "Internal error".
Trying s3curl I see the following:
1) Listing the Buckets works fine
# s3curl.pl --id=dajoha -- --insecure https://iddjo02.uzh.ch:9021
2) Listing an empty Bucket also works fine
# s3curl.pl --id=dajoha -- --insecure https://iddjo02.uzh.ch:9021/emctest
3) Listing a Bucket with object in it fails
# s3curl.pl --id=dajoha -- --insecure https://iddjo02.uzh.ch:9021/blabla
InternalErrorAny suggestions?
D/\N