Hi, I’ve setup risk-cs (2.1.0) on a linux (ubuntu 15.04) box to start learning and followed the Riak Fast Track guide. I am trying to use s3cmd (version 1.5.0-rc1) to interact with riak-cs in a proxy configuration (not direct).
However, any attempt to create a bucket fails with 403. My s3cmd config looks like: [default] access_key = IIQHN7RPFVCIGO6AWUPC secret_key = E60Y6vojRnZXMZRILe-Dw3V7azVnE9IjI6XaeQ== bucket_location = US cloudfront_host = cloudfront.amazonaws.com cloudfront_resource = /2010-07-15/distribution default_mime_type = binary/octet-stream delete_removed = False dry_run = False enable_multipart = False encoding = UTF-8 encrypt = False follow_symlinks = False force = False get_continue = False gpg_command = /usr/local/bin/gpg gpg_decrypt = %(gpg_command)s -d --verbose --no-use-agent --batch --yes --passphrase-fd %(passphrase_fd)s -o %(output_file)s %(input_file)s gpg_encrypt = %(gpg_command)s -c --verbose --no-use-agent --batch --yes --passphrase-fd %(passphrase_fd)s -o %(output_file)s %(input_file)s gpg_passphrase = password guess_mime_type = True host_base = s3.amazonaws.com host_bucket = %(bucket)s.s3.amazonaws.com human_readable_sizes = False list_md5 = False log_target_prefix = preserve_attrs = True progress_meter = True proxy_host = localhost proxy_port = 8080 recursive = False recv_chunk = 4096 reduced_redundancy = False send_chunk = 4096 simpledb_host = sdb.amazonaws.com skip_existing = False socket_timeout = 300 urlencoding_mode = normal use_https = False verbosity = WARNING signature_v2 = True I have riak, stanchion, and risk-cs configured per the Fast Track guide, and all are up and running (can ping, etc.). Any ideas how I might figure out what the issue is? Thanks! — Regards, Devin _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
