I personally not sure what happens here, but:
Just opening http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/natty-updates/ in a browser leads to 403 XML. Ok, suppose it's limited to only EC2. From out EC2 machine:
ubuntu@ip-10-243-34-224:~$ wget http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/natty-updates/ --2012-04-06 15:36:06-- http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/natty-updates/ Resolving us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com... 72.21.214.160 Connecting to us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com|72.21.214.160|:80... connected. HTTP request sent, awaiting response... 403 Forbidden 2012-04-06 15:36:06 ERROR 403: Forbidden.
But, any url of http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/* leads to 403. So again, I'm not sure this is really a bug vs something we don't know how to use.
I personally not sure what happens here, but:
Just opening http:// us-east- 1.ec2.archive. ubuntu. com.s3. amazonaws. com/ubuntu/ dists/natty- updates/ in a browser leads to 403 XML. Ok, suppose it's limited to only EC2. From out EC2 machine:
ubuntu@ ip-10-243- 34-224: ~$ wget http:// us-east- 1.ec2.archive. ubuntu. com.s3. amazonaws. com/ubuntu/ dists/natty- updates/ us-east- 1.ec2.archive. ubuntu. com.s3. amazonaws. com/ubuntu/ dists/natty- updates/ 1.ec2.archive. ubuntu. com.s3. amazonaws. com... 72.21.214.160 1.ec2.archive. ubuntu. com.s3. amazonaws. com|72. 21.214. 160|:80. .. connected.
--2012-04-06 15:36:06-- http://
Resolving us-east-
Connecting to us-east-
HTTP request sent, awaiting response... 403 Forbidden
2012-04-06 15:36:06 ERROR 403: Forbidden.
But, any url of http:// us-east- 1.ec2.archive. ubuntu. com.s3. amazonaws. com/* leads to 403. So again, I'm not sure this is really a bug vs something we don't know how to use.