search

spring-attic / aws-maven

Apache License 2.0
214 stars 174 forks source link

AWS STS credentials do not work #49

Open dball opened 8 years ago

dball commented 8 years ago

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 commented 7 years ago

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 commented 7 years ago

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 commented 6 years ago

@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 commented 6 years ago

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: https://github.com/s3-wagon-private/s3-wagon-private/issues/30

Your version works - also requires AWS_REGION.