[Bug 615545] Re: Instances launched in a VPC cannot access ec2.archive.ubuntu.com

[Noah]

I agree with Eric and cloudcontrol, for CNAMEs being the correct
solution.

In the meantime, there's a problem with using any debian package from
within ec2 instances - you can't contact the repository to install any
packages, so using a package to fix the problem presents something of a
bootstrapping problem.

That includes, by the way, anything that requires apt-mirror, since apt-
mirror is not part of the barebones Lucid AMI, and thus requires
installation, which requires connecting to the repo...

I have an alternative solution, which requires no package installation,
and which I will be using until this problem is fixed. Rather than
installing packages, I have chosen the simpler direct manipulation of
the sources.list file, like this:


sed -i -e 's/eu-west-1.ec2/uk/' /etc/apt/sources.list

Change 'uk' to be whatever your closest mirror is, and you'll be running
again.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/615545

Title:
  Instances launched in a VPC cannot access ec2.archive.ubuntu.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/615545/+subscriptions