I have been using s3curl.sh with success to do the dirty work with Riak CS. 
Here’s a snippet from my docker setup files. I use the same methodology in 
production.

187   # CREATE CS BUCKET AND APPLY ACL 
 188   ## 
 189   bin/s3curl.pl \ 
 190       --debug \ 
 191       --id ${RIAK_ADMIN_KEY} \ 
 192       --key ${RIAK_ADMIN_SECRET} \ 
 193       --acl private \ 
 194       -- -s -v -x social.dev.pryvy.com:50201 \
 195       -X PUT http://social-media.cs.pryvy.com/ > /dev/null 2>&1
 196   echo "    created social-media bucket" 
 197  
 198   eval "bin/s3curl.pl --debug --id ${RIAK_ADMIN_KEY} --key 
${RIAK_ADMIN_SECRET} -- -s -v -x social.dev.pryvy.com:50201 -H 
'x-amz-grant-full-control: id=\"${RIAK_A     DMIN_ID}\"' -H 'x-amz-grant-write: 
id=\"${RIAK_SOCIAL_ID}\"' -X PUT http://social-media.cs.pryvy.com/?acl";  > 
/dev/null 2>&1 
 199   echo "    applied social bucket policy"


Also, when applying the ACL, it has to evaluated as shown above if you are 
using bash as your shell.

HTH,
Shawn




On 10/13/15, 1:24 AM, "riak-users on behalf of G" 
<riak-users-boun...@lists.basho.com on behalf of m.gnanen...@yahoo.co.in> wrote:

>Hi Shino,
>
>I tried multiple times with the access key and secret key configured in
>riak-cs.conf. But I'm unable to create or view buckets using s3 cmd.
>
>Could you let me know if there is any documentation for this? 
>
>My aim to create buckets, upload objects to riak buckets from a HTTP
>interface similar to aws - s3. 
>
>
>
>--
>View this message in context: 
>http://riak-users.197444.n3.nabble.com/Riak-CS-Unable-to-create-view-bucket-details-using-dragon-disk-tp4033494p4033579.html
>Sent from the Riak Users mailing list archive at Nabble.com.
>
>_______________________________________________
>riak-users mailing list
>riak-users@lists.basho.com
>http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Reply via email to