Highlighted
3 Silver

Where are Amazon S3 and Google(or EMC ECS) S3 different?

Jump to solution

I find out that the methods of validation cloud storage credential between Google S3 and Amazon S3 are different. Google S3(or EMC ECS) use " java -jar blobstore-cli.jar --provider s3 --endpoint <endpoint URL> --identity <access key> --credential <secret key> validate", and Amazon S3 use " java -jar blobstore-cli.jar --provider aws-s3 --identity <access key> --credential <secret key> validate".Is there any different in using "s3" or "aws-s3"?

0 Kudos
1 Solution

Accepted Solutions
Highlighted
2 Bronze

Re: Where are Amazon S3 and Google(or EMC ECS) S3 different?

Jump to solution

Not really. With aws-s3 you just don't need to define the url of the endpoint because it will know to use s3.amazonaws.com.

View solution in original post

0 Kudos
6 Replies
Highlighted
2 Bronze

Re: Where are Amazon S3 and Google(or EMC ECS) S3 different?

Jump to solution

Not really. With aws-s3 you just don't need to define the url of the endpoint because it will know to use s3.amazonaws.com.

View solution in original post

0 Kudos
Highlighted
3 Silver

Re: Where are Amazon S3 and Google(or EMC ECS) S3 different?

Jump to solution

Thanks a lot for you answer. One more question, I log CB as maginatics user and I find out that the "/opt/maginatics/jclouds/bin/" directory has a program named "jclouds". And "jclouds" command includes blobstore blob-exists, blobstore blob-container-clear, group destory, node create, node list and so on. I want to know whether "jclouds group * " or "jclouds node * " or "jclouds image * " or "jclouds location list " is used to communicate with cloud storage ?

jcloud command:

maginatics@cloudboost1:/opt/maginatics/jclouds-cli/bin$ ./jclouds

Command not found: Usage: jclouds {category} {action} {options/arguments}

Valid commands:

    blobstore blob-exists

    blobstore blob-metadata

    blobstore container-clear

    blobstore container-create

    blobstore container-delete

    blobstore container-exists

    blobstore container-list

    blobstore container-metadata

    blobstore list

    blobstore location-list

    blobstore read

    blobstore remove

    blobstore write

    group destroy

    group runscript

    hardware list

    image create

    image list

    location list

    node create

    node destroy

    node destroy-all

    node info

    node list

    node resume

    node runscript

    node suspend

Options:

    --properties: File containing properties

    --provider:   The id of the provider

    --api:        The id of the api

    --endpoint:   The endpoint

    --identity:   The identity

    --credential: The credential

0 Kudos
Highlighted
2 Bronze

Re: Where are Amazon S3 and Google(or EMC ECS) S3 different?

Jump to solution

jclouds is an open source multi-cloud toolkit that has many other features. CloudBoost only uses the subset related to object storage.

0 Kudos
Highlighted
3 Silver

Re: Where are Amazon S3 and Google(or EMC ECS) S3 different?

Jump to solution

So, does CloudBoost only use "./jclouds blobstore * " command to communicate with object storage ?

0 Kudos
Highlighted
2 Bronze

Re: Where are Amazon S3 and Google(or EMC ECS) S3 different?

Jump to solution

That is correct only the blobstore commands are used. CloudBoost does not create any compute resources in the cloud.

0 Kudos
Highlighted
3 Silver

Re: Where are Amazon S3 and Google(or EMC ECS) S3 different?

Jump to solution

OK ,Thank you so much.

0 Kudos