Skip to content
This repository has been archived by the owner on Apr 30, 2019. It is now read-only.

AWS STS credentials do not work #49

Open
dball opened this issue Aug 17, 2016 · 4 comments
Open

AWS STS credentials do not work #49

dball opened this issue Aug 17, 2016 · 4 comments

Comments

@dball
Copy link

dball commented Aug 17, 2016

I prefer to use aws-vault to issue temporary credentials for day-to-day AWS operations. Apparently AWS STS credentials don't work correctly until aws-java-sdk 1.8.0, while the latest release of aws-maven uses aws-java-sdk 1.7.1.

It would be cool to see a release that used a later version of aws-java-sdk.

@lewisd32
Copy link

I'd love to see this fixed too, as it conflicts with our desire to normally run as a low-privilege user, and use assume-role to get write-access to the repository.

I notice there's no commits to this repo since 2014. Is it a dead project? Is there an alternative for deploying to S3 repos?

@dball
Copy link
Author

dball commented Nov 16, 2016

I wrote a maven that uses the AWS CLI to sidestep this whole mess. It's written in and for clojure but may be usable for other jvm projects: https://github.com/SparkFund/aws-cli-wagon

@moleksyuk
Copy link

@dball

Try our fork. It was updated to the latest aws-sdk:1.11.276.

<dependency>
    <groupId>com.github.platform-team</groupId>
    <artifactId>aws-maven</artifactId>
    <version>6.0.0</version>
</dependency>

@bemowski
Copy link

bemowski commented Mar 8, 2018

Thank you @moleksyuk. Been fighting with this all day. Was trying the spring aws-maven, and the maven-s3-wagon, both of which use pre 1.8.0 aws java libraries which do not accept temporary tokens. (found that here: s3-wagon-private/s3-wagon-private#30

Your version works - also requires AWS_REGION.

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

No branches or pull requests

4 participants