You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 30, 2019. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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?
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
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I prefer to use
aws-vault
to issue temporary credentials for day-to-day AWS operations. Apparently AWS STS credentials don't work correctly untilaws-java-sdk
1.8.0, while the latest release ofaws-maven
usesaws-java-sdk
1.7.1.It would be cool to see a release that used a later version of
aws-java-sdk
.The text was updated successfully, but these errors were encountered: