-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Amazon areas #1
Comments
bpo
referenced
this issue
in bpo/apt-s3
May 4, 2012
Update README.md with build instructions and reorg
@kyleshank You don't want to include this? Would be helpful! :) |
I bumped into the same problem and solved it using the DNS-specific endpoints available for each region. For example:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
It seems like apt-s3 works only with amazon US Standard area.
I tried setting up an apt repo on eu-east-1 with no luck. I tried s3://AWS_ACCESS_ID:[AWS_SECRET_KEY_IN_BRACKETS]@s3.amazonaws.com/BUCKETNAME and s3://AWS_ACCESS_ID:[AWS_SECRET_KEY_IN_BRACKETS]@BUCKETNAME.s3.amazonaws.com/ URLs with no more luck.
Did I miss something?
Thanks for your time and help.
Brice.
P.S.: I used https://github.com/mbbx6spp/apt-s3/ fork to get it to compile with no brain.
The text was updated successfully, but these errors were encountered: