Using S3FS to mount S3 bucket? Point me in the right direction.

I’m having a lot of trouble mounting S3 on an (Linode) based instance. This instance didn’t come bundled with Wowza, just to be clear. Wowza is installed and running fine. Nevertheless, I can’t seems to see any directories I try to mount. I’ve done the following:

bash$ brew install s3fs

bash$ brew info fuse4x-kext

(Copy and Paste …fuse4x.kext and …load_fuse4x from the info command above)

bash$ sudo /bin/cp -rfX /usr/local/Cellar/fuse4x-kext/0.9.2/Library/Extensions/fuse4x.kext /Library/Extensions

bash$ sudo chmod +s /Library/Extensions/fuse4x.kext/Support/load_fuse4x

bash$ sudo chmod +s /System/Library/Extensions/fuse4x.kext /Support/load_fuse4x

bash$ echo “AWSACCESSKEYID:AWSSECRETACCESSKEY” > ~/.passwd-s3fs

bash$ chmod 600 ~/.passwd-s3fs

bash$ mkdir /Volumes/s3

bash$ /usr/local/bin/s3fs BUCKETNAME /Volumes/s3 -olocal,ping_diskarb,volname=S3

s3fs: bucket BUCKETNAME is not part of the service specified by the credentials

bash$ open /Volumes/s3

The error I’m seeing:

s3fs: bucket BUCKETNAME is not part of the service specified by the credentials

Also to be clear, I’m using S3 elsewhere in the application. I’m registered. The credentials are correct. This error is something else I think, like a false positive. Additionally, BUCKETNAME is just a variable in this example. It can be anything e.g. - “FooBarBucket”. My guess is this, either a command above is wrong or I’m missing something else entirely… both likely.

One more thing, the command list above was run locally and verified on OS X, so neither the Linode instance nor my MBP were able to see any directories.

Appreciate any input.

I’m putting a “solution” here for posterity. Panic’s Transmit has the ability to mount S3 buckets. This works, but I’d still like to know what was wrong with the previously run commands. Thanks.

http://panic.com/transmit/