Sorry, I should have been clear in the original bug report that I was submitting it on behalf of Amazon and another customer and did not experience it myself on that particular instance or AMI.
Also, I'm not sure that "lack of a public IP" address as described in #615545 is sufficient to determine if you are in VPC now-a-days. When VPC was launched, all instances were entirely private, but Amazon later released the ability for a VPC instance to have a public IP address with direct Internet access as an optional feature depending on the customer's security policies. Modifying Canonical's DNS seems like the best approach to support current and future AWS services and features. Using a CNAME to an Elastic IP Address transfers the burden to Amazon for determining how the instance should access the apt repository (internal or external). -- 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/824947 Title: EC2 apt repository DNS resolution on VPC instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/824947/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
