| posting from a mail from Gabriel: | | The design of VPC is that instances launched in VPC cannot communicate with | the internal EC2 network. They can only communicate with other instances in | the subnet, and the machines on the other end of the tunnel. All internet | traffic is routed through the customer's internet connection. I don't see | any possibility to enable communication with the internal ec2 network. | | Would any of my suggestions listed in the bug work? Eg, use lack of a public | ip, or adding the public ubuntu archive as a fallback?
Yeah, you're probably right, lack of public ip would probably work. We may be able to check for reachability of the mirror in DataSourceEc2. Right now we just check that it resolves. 2 things you can easily do to work around this issue: 1.) launch instances with user data like: #cloud-config apt_mirror: http://us.archive.ubuntu.com/ubuntu/ The above will allow other portions of cloud-config that assume apt is set up properly to work. 2.) grab the apt-mirror from /etc/apt/sources.list and add an entry in /etc/hosts to point to whatever is right for you. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
