How to configure to communicate with S3 clones?

[akiradeveloper]

If I understand correctly your goal is to access filesystems and S3 storages transparently. Good tool. I want to use mc instead of s3cmd.

I am considering If I could pass destination address, port number, the version of authentication scheme (v2 or v4), auth key, secret key and so on that's required to communicate with S3 clones like Riak CS.

Can we write config file like s3cmd and set up for S3 clones?

[akiradeveloper]

sorry. I missed this sentence in README "Update AccessKeyID and SecretAccessKey fields in your ~/.mc/config.json configuration file"

[akiradeveloper]

what's milkyway...? mc uses unusual region so this tool is only for minio, not for other clones. did you test with AWS S3? it should be sending with v2 authentication that's region irrelevant so to talk with any clones.

[harshavardhana]

what's milkyway...? mc uses unusual region so this tool is only for minio, not for other clones. did you test with AWS S3? it should be sending with v2 authentication that's region irrelevant so to talk with any clones.

mc only supports AWS S3 Signature v4, We do not support signature v2.

For now mc tool is only tested for minio and AWS S3 not other clones. We are not planning on supporting signature V2 any time soon.

If RiakCS supports signature V4 then mc can be made to work with RiakCS with few changes.

[harshavardhana]

Easiest way to add your keys for s3 is simple as shown below.

$ mc config host help
....
....
   1. Add host configuration for a URL. For security reasons turn off bash history
      $ set +o history
      $ mc config host add s3.amazonaws.com BKIKJAA5BMMU2RHO6IBB V7f1C\wQqAcwo80UEIJEjc5gVQUSSx5ohQ9GSrr1
      $ set -o history

   2. List all hosts.
      $ mc config host list

   3. Remove host config.
      $ mc config host remove s3.amazonaws.com

[akiradeveloper]

Thanks.

Heard that you aren't going to make v2 signature available soon but you think it's possible to implement v2? I don't know why you didn't implement v2 that's even easier than v4

[harshavardhana]

Heard that you aren't going to make v2 signature available soon but you think it's possible to implement v2? I don't know why you didn't implement v2 that's even easier than v4

It is our belief to keep things minimal that we only do one way to do one thing. Given a choice if it is signatureV2 v/s signatureV4 - it was signatureV4.

mc is designed to work for S3 first for all regions, so it does what Amazon S3 recommends. Even minio server had to implement signature V4 to be compatible with mc. We choose "milkyway" as the default region for minio.

[akiradeveloper]

I understand your belief but still I want v2 signature. The biggest reason is to use mc for S3 storage software that I am implementing now (which only supports v2). I tried s3cmd and s4cmd but they weren't good enough.

Do you think it is possible to support v2 signature by generalizing signing process? (like defining Singer like in AWS SDK http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/Signer.html). I think the code below is signing the request.

// Do - start the request
func (r *request) Do() (resp *http.Response, err error) {
        if r.config.AccessKeyID != "" && r.config.SecretAccessKey != "" {
                r.SignV4()
        }

[harshavardhana]

I understand your belief but still I want v2 signature. The biggest reason is to use mc for S3 storage software that I am implementing now (which only supports v2). I tried s3cmd and s4cmd but they weren't good enough.

Okay let's see - if we can make it work. I will need some time to get this working..

// Do - start the request
func (r *request) Do() (resp *http.Response, err error) {
if r.config.AccessKeyID != "" && r.config.SecretAccessKey != "" {
r.SignV4()
}

Signing process can be generalized.

[akiradeveloper]

Thanks. I am looking forward to it.