When launching ec2-instances in VPN they have no internet access when they have no public ip (not elastic ip!).
The run-instances command has an option --associate-public-ip-address which allocates one, and allows internet access e.g. maven-repo read.
Currently the agent-cloud configuration of TC does not allow the property to be set.
Is anybody running ec2-agents in a VPC with access to the internet?