Comment 6 for bug 907450

The problem in this case is that Walrus is breaking the convention established by the real S3 of owning the full path namespace of the TCP address that hosts the service.

So, while in S3 you'd access <addr>/bucket-name/key, in Walrus one has to use something like <addr>/path/for/walrus/bucket-name/key

It's not a big deal, but it's unconventional, and libraries have to be adapted to support it. IIRC, even boto itself, which is used in Eucalytpus tools, had to be patched by them to support that.