Public bug reported:

sources.list is helpfully configured to us-east-1.ec2.archive.ubuntu.com
for instances that I launch in US-EAST-1 on EC2. However, instances
launched in a Virtual Private Cloud (VPC) can only access machines in
their local subnet, private machines on the connected LAN, and the
Internet via the VPC tunnel.

Because us-east-1.ec2.archive.ubuntu.com resolves to an internal EC2
10.0.0.0/8 address, instances launched in a VPC will be unable to
perform any apt operations. The user must update sources.list to point
to us.archive.ubuntu.com to use apt.

Proposed solution:

1) Detect that the machine was launched in a VPC. I'm not sure what the ideal 
way to determine this is without doing a DescribeInstances. But I did notice 
that when in a VPC, curl http://169.254.169.254/latest/meta-data/ does not have 
public-ipv4 and public-hostname listed as a possibility. So perhaps the absence 
of these could be used to determine it was in a VPC.
2) Fallback to the public us.archive.ubuntu.com (or whatever region 
appropriate) if us-east-1.ec2.archive.ubuntu.com cannot be reached.

** Affects: linux-ec2 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Instances launched in a VPC cannot access ec2.archive.ubuntu.com
https://bugs.launchpad.net/bugs/615545
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to