Getting aws_key and as_secret in CI environment

[faceleg]

I want to use this awesome repo as a mock for tests running in a CI environment. This is for node-s3-client.

How do I get the AWS_KEY and AWS_SECRET in this situation? Is it randomly generated each time s3ninja is started or static?

[scireumskip]

It is static. We use the credentials used by the examples from Amazon.
Am 25.01.2016 1:22 vorm. schrieb "Michael Robinson" <
[email protected]>:

I want to use this awesome repo as a mock for tests running in a CI
environment. This is for node-s3-client.

How do I get the AWS_KEY and AWS_SECRET in this situation? Is it randomly
generated each time s3ninja is started or static?

—
Reply to this email directly or view it on GitHub
#52.

[faceleg]

Ok thanks!

I also seem to be suffering from the "401 all the things" syndrome.

Is there anything special I have to do other then using the right secret and key?

This is the code: andrewrk/node-s3-client#119

And thanks for making this tool, it's great!

One more thing - I "dockerised" it:

• https://hub.docker.com/r/66pix/s3ninja/

[andyHa]

Is the problem still presistent? We use the latest SDK from aws along with the latest version of s3ninja and it works great...

[faceleg]

I haven't had time to try again since your comment, if I do I'll come back and report

[andyHa]

We now provided a new release which fixes a bunch of issues concerning signed chunks / uris / ...

The credentials as fixed (in application.conf) and by default the ones from the S3 examples^^. You can provide a custom config to overwrite them or to supply custom ones via env variable.

Also, there is now an "official" docker image: https://hub.docker.com/r/scireum/s3-ninja - feel free to provide any suggestions / improvments....