Is jclouds EC2 support compromised by this?
I'm not sure if this fully answers your question, Duncan, but with jclouds you *can* specify the VPC into which you want your instance launched, although (from memory) you need the AWS-specific API to do so.
So I can't say whether things still work nicely "by default", but it should still be possible to launch instances successfully even after this change.
Hope this helps! ap
