Re: [Duplicity-talk] Configurable amazon s3 host - WAS: Fwd: Re: [Duplicity-team] [Question #150801]: BucketAlreadyOwnedByYou

[edgar . soldin]

Are you sure? 

http://aws.amazon.com/articles/3912#s3

As far as I understand by reading
http://docs.amazonwebservices.com/AmazonS3/latest/dev/LocationSelection.html
you either use the host or the LocationConstraint. But hey, why not supporting 
a host in url *and* a --s3-locationconstraint parameter. Just in case it is 
needed.

I definitely think we should only define the default host. If someone wants to 
use the specific locations he should read the pages above and define the 
correct params himself. 

Don't you think?..ede


On 20.08.2011 13:52, Kenneth Loafman wrote:
> It's not just a matter of changing the endpoint, it's the 
> 'LocationConstraint' value for the bucket as well.  It seems this could be a 
> sticky point.
> 
> I'd be willing to make the change, but I've got no way to test in other 
> regions.
> 
> ...Ken
> 
> On Sat, Aug 20, 2011 at 6:03 AM, <address@hidden <mailto:address@hidden>> 
> wrote:
> 
>     Does anybody using S3 want to step up and tackle this? It' quite easy to 
> implement. Also any offer doublechecking the change is apreciated.
> 
>     ede/duply.net <http://duply.net>
> 
>     -------- Original Message --------
>     Subject: Re: [Duplicity-team] [Question #150801]: BucketAlreadyOwnedByYou
>     Date: Thu, 11 Aug 2011 10:51:53 +0200
>     From: address@hidden <mailto:address@hidden>
>     To: address@hidden <mailto:address@hidden>
>     CC: address@hidden <mailto:address@hidden>
> 
>     as this is obviously official functionality this should be configurable. 
> why don't we actually do not support to put these in the target url, maybe 
> optionally?
> 
>     ..ede/duply.net <http://duply.net>
> 
>     On 11.08.2011 10:36, Brandon Keszler wrote:
>     > Question #150801 on Duplicity changed:
>     > https://answers.launchpad.net/duplicity/+question/150801
>     >
>     > Brandon Keszler proposed the following answer:
>     > Max, I just came across this same issue this evening. I see the thread
>     > hasn't been updated in a while but wanted to post for anyone else that
>     > may be frustrated with this.
>     >
>     > You can force duplicity to use the Northern California buckets (even 
> existing ones) by editing 'connection.py' in the python modules folder (for 
> me: /usr/lib/pymodules/python2.6/boto/s3). There are only two lines that need 
> to be changed (->) as follows:
>     > ---------------
>     > connection.py:91
>     > DefaultHost = 's3.amazonaws.com <http://s3.amazonaws.com>' -> 
> DefaultHost = 's3-us-west-1.amazonaws.com <http://s3-us-west-1.amazonaws.com>'
>     >
>     > connection.py:214
>     >  url = '%s://%s.s3.amazonaws.com/ <http://s.s3.amazonaws.com/>' % 
> (http_method, bucket_name) -> url = '%s://%s.s3-us-west-1.amazonaws.com/ 
> <http://s.s3-us-west-1.amazonaws.com/>' % (http_method, bucket_name)
>     > ---------------
>     > If you need to use other regions (i.e. Tokyo), simply substitute with 
> the region specific endpoints per the AWS documentation
>     > http://aws.amazon.com/articles/3912#s3
>     >
> 
> 
>     _______________________________________________
>     Duplicity-talk mailing list
>     address@hidden <mailto:address@hidden>
>     https://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 
> 
> 
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk