Credentials can't be configured

[c24w]

You must now specify a specific set of credentials for signed request work. Use S3RVER for both the Access Key ID and Secret Access Key.

This is fine, but we're using other AWS services in the same app. This means we'd have to configure the AWS SDK to use different credentials only when using S3, creating test-specific implementation.

We'd prefer to only configure the AWS SDK once with the same test credentials; It would be handy to make the dummy credentials configurable when starting s3rver.

[adam-nielsen]

Ah, just wondered why everything broke when I updated serverless-s3-local. Definitely can't change the credentials because we are using them to read data from live databases and want to write to the local S3 instance.

Is there some way we can go back to the old behaviour where the credentials are just ignored?

[adam-nielsen]

FYI for anyone else having this problem, downgrading with npm install [email protected] dropped me back to s3rver 2.2.5 which got everything working again.

[fishcharlie]

I believe this will be fixed in #598? Is that what you are looking for or something else?

[c24w]

Yep, that looks about right! :)

[scooper91]

@kherock @leontastic Is there any way we can get this issue moving again? It's something we're struggling with at the moment, as we need to talk to this, and a real AWS service in the same application (for local testing).

There seem to be two open pull requests related to it - #598 and #682.