Szymon Jednac

Having the default resolver settings should be enough since #1 was introduced (9729e1f). Did you experience any issues with the base setup in that matter?

Just to clarify - are you using the latest version for the moment (i.e. `0.10.0`) or the one from the blog post?

Thanks for pointing this out! I'm observing https://github.com/sbt/sbt/issues/6294 for a consistent approach - I'd expect a change in the upcoming week, since it seems to have reached a conclusion.

This could be a nice extension indeed. The main issue I'm seeing are priorities for the config - we should probably keep the [same order](https://github.com/sbilinski/sbt-ecr/blob/master/src/main/scala/sbtecr/Aws.scala#L15) as in the authentication chain....

Hi @eugenemiretsky, Did you run `ecr:login` before `ecr:push`? A successful login should look something like this in the current plugin version (from the `sbt` shell): ``` [my-project] $ ecr:login [info]...

Hi @neowulf33, I'm not sure why `sys.env.getOrElse("AWS_DEFAULT_PROFILE", "default")` returns `shared` in your context as `-D` would suggest a JVM system property, not an environment variable as expected by the plugin....

I'm not sure what could go wrong here, since repository creation is just a direct call to the Amazon SDK. That being said, does it work if you put your...

> Do you know if the role within the aws profile gets automatically picked up by the AWS Java SDK? I suppose the role is inherited from the `aws_access_key_id`. >...

Credential providers are taken in order, until some value is found. Maybe you should check if there is no `AWS_ACCESS_KEY_ID` or `AWS_ACCESS_KEY` in your environment variables as they will [override](http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/EnvironmentVariableCredentialsProvider.html)...

@neowulf33: Given the content of the PR and the comment above, I think the main issue is that you need to assume the role **before** you run any plugin commands...