RiakCS - AWS-CLI command works but Node.js API fails

Shunichi Shinohara shino at basho.com
Thu Dec 3 04:43:12 EST 2015


It seems that it's related with an trouble with server certificates
with wildcard domain and client side verification. A dot(".") in
"wildcard part", "service-instance-ee57eed6-6f95-4de3-b2c7-6b787c11e922.riakcs"
in your example, may make things complicated? ... but I'm sorry that I'm
not very good at the area.
Quick search shows something may/may not related, e.g. [1]

[1] https://github.com/Automattic/knox/issues/153

Thanks,
Shino

2015-12-03 18:22 GMT+09:00 Dattaraj Rao <dattarajrao at yahoo.com>:
> Error message is:
>
> Error: Hostname/IP doesn't match certificate's altnames: "Host:
> service-instance-ee57eed6-6f95-4de3-b2c7-6b787c11e922.riakcs.system.aws-usw02-pr.ice.predix.io.
> is not in the cert's altnames: DNS:*.system.aws-usw02-pr.ice.predix.io,
> DNS:system.aws-usw02-pr.ice.predix.io"
>
> My code is - i also tried on tonicdev - same error:
> var AWS = require('aws-sdk');
>
> AWS.config.update({sslEnabled: true, accessKeyId: 'DJDTSN2GITBEL4QMPXKN',
> secretAccessKey: 'z2NeYH7R3VfNOOARvHHe5MAKM7pGkc66MWU_VA==', endpoint:
> 'https://riakcs.system.aws-usw02-pr.ice.predix.io/'});
>
> var s3 = new AWS.S3();
>
> s3.getObject({Bucket:
> 'service-instance-ee57eed6-6f95-4de3-b2c7-6b787c11e922', Key: 'lvision_1'},
> function (err, data) {
>   if(err)
>     console.log("Error - ", err);
>   if(data)
>     console.log("Data - ", data);
> });
>
> console.log('test');
>
>
> Regards,
> Dattaraj Jagdish Rao
> http://www.linkedin.com/in/dattarajrao
>
>
>
>
> On Thursday, December 3, 2015 2:43 PM, Shunichi Shinohara <shino at basho.com>
> wrote:
>
>
> Thanks for update. Then, please let me ask some questions:
>
> - What was the actual error message?
> - Could you confirm your code / SDK generate network communication
>   to Riak CS?
>
> Shino
>
> 2015-12-01 17:18 GMT+09:00 Dattaraj J Rao <dattarajrao at yahoo.com>:
>> Thanks Shino for your response.
>>
>> I tried providing the buclet url as endpoint - also tried setting
>> s3endpoint to true. Same problem.
>>
>> Surprisingly the command line tool works fine.
>>
>> Regards,
>> Dattaraj
>> http://in.linkedin.com/in/dattarajrao
>>
>> -----Original Message-----
>> From: Shunichi Shinohara <shino at basho.com>
>> Date: Mon, 30 Nov 2015 10:26:48
>> To: Dattaraj Rao<dattarajrao at yahoo.com>
>> Cc: riak-users at lists.basho.com<riak-users at lists.basho.com>
>> Subject: Re: RiakCS - AWS-CLI command works but Node.js API fails
>>
>> Hi Dattaraj,
>>
>> I'm not sure how AWS SDK JS works in detail, I'm wondering whether
>> it's good to include
>> S3/CS bucket name in endpoint string.  One example of the doc [1], it does
>> not
>> have bucket name part.
>>
>> [1] http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Endpoint.html
>>
>> Thanks,
>> Shino
>>
>> 2015-11-28 23:13 GMT+09:00 Dattaraj Rao <dattarajrao at yahoo.com>:
>>> Hello,
>>> I am trying to access a RiakCS data store. I can access it using
>>> following
>>> command in AWS-CLI:
>>>
>>> $ aws s3 --endpoint-url https://my-riak-address.io cp my-local-file
>>> s3://service-instance-e689c062-dee6-45d7-90fe-39e63256915f
>>>
>>> However when I try connecting to same repository using Node JS and
>>> AWS-SDK
>>> bunlde - it does not connect. Says endpoint not exposed.
>>>
>>> var AWS = require('aws-sdk');
>>> AWS.config.update({accessKeyId: 'mykey', secretAccessKey: 'mysecret'});
>>>
>>> var ep = new
>>>
>>> AWS.Endpoint('https://my-riak-address.io/service-instance-e689c062-dee6-45d7-90fe-39e63256915f');
>>> var s3 = new AWS.S3({endpoint: ep});
>>>
>>>
>>> Regards,
>>> Dattaraj
>>>
>>> _______________________________________________
>>> riak-users mailing list
>>> riak-users at lists.basho.com
>>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>>>
>
>




More information about the riak-users mailing list