Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

node-s3-cli with Digital Ocean Spaces #39

Open
gsiotas opened this issue Jan 24, 2018 · 2 comments
Open

node-s3-cli with Digital Ocean Spaces #39

gsiotas opened this issue Jan 24, 2018 · 2 comments

Comments

@gsiotas
Copy link

gsiotas commented Jan 24, 2018

After searching through and following this comment, I managed to make the node-s3-cli work with Digital Ocean Spaces (DO Spaces).
In the config file "~/.s3cfg" just put the default configuration:

[default]
access_key = foo
secret_key = bar

Of course you have to change the foo and the bar according to the data you receive from DO API page.

Then on the file cli.cfg, usually found at:

/usr/local/lib/node_modules/s3-cli

you change the following:

  client = s3.createClient({
    s3Options: {
      accessKeyId: accessKeyId,
      secretAccessKey: secretAccessKey,
      sslEnabled: !args.insecure,
      region: args.region,
endpoint: 'ams3.digitaloceanspaces.com',
    },

Basically you enter the endpoint endpoint: 'ams3.digitaloceanspaces.com', change according to the location of your space.

If I won't hardcore the endpoint I get this error message:

Error: The AWS Access Key Id you provided does not exist in our records.

Thank you!

@thecatontheflat
Copy link

Thank you for figuring this, it helped!

@KieronWiltshire
Copy link

I'll fork the project and submit a pull request so that maybe this will be included in the next release. Thanks for figuring this out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants