-
Notifications
You must be signed in to change notification settings - Fork 174
Endpoint Support #4
Comments
I'll take a look at this in a bit and get a fix out. Thanks for letting me know. |
Previously, if a bucket from a non-US region was accessed, a failure would occur. Now, the wagon attempts to determine what endpoint the bucket should be accessed at, and then uses that endpoint for all future access. In order to determine the endpoint of a bucket, you must have provided credentials that are privileged enough to read the metadata of that bucket. Closes issue #4
This should be fixed in 4.5.0.RELEASE which will show up shortly in various repositories. Please take note of the caveat about credentials in the commit log (I'm betting that you're already configured properly for this to work), and let me know if you've got any problems with it. |
Works in 4.8.0.RELEASE with CNames configuration. Users should update from 4.5.0.RELEASE |
@koppor sorry I know this is old but do you happen to remember what you mean by "CNames configuration"? I was hoping aws-maven lets you configure the endpoint directly, making requests to
This way it could publish to any S3-compatible storage system, not only AWS. The bucket name just needs a CNAME DNS record that points to the S3-compatible server. But aws-maven always uses url Seems it would be easy to add an option to use the |
Anyone that ends up here looking to |
This is happening to me as well, with a user with full s3 access. 5.0.0.RELEASE |
I currently use Japan S3 bucket and this plugin does not support uploading to S3 repos other than the standard US S3 buckets.
The text was updated successfully, but these errors were encountered: