Hi,
We changed the API version on libcloud/libcloud/compute/drivers/ec2.py from API_VERSION = '2010-08-31' to API_VERSION = '2013-02-01' and this hasn't created issues for all actions we tested -create/destroy/reboot/shutdown/tag machine. With the previous API, on newly created ec2 accounts functions ex_authorize_security_group* failed, so ssh wasn't allowed on machines created. That is because new accounts in ec2 are launched with VPC by default, with the VPC features being available to existing accounts launching instances in a Region for the first time. http://aws.typepad.com/aws/2013/03/amazon-ec2-update-virtual-private-clouds-for-everyone.html https://forums.aws.amazon.com/thread.jspa?messageID=472353񳔡 Obviously I don't suggest that libcloud changes the API version for ec2, since we haven't tested extensively that it does not break things ;) Regards Στις 10.09.2013 00:54, Tomaz Muraus έγραψε: > Hi, > > I don't have experience with those recent changes, but I assume you are > talking about this http://aws.amazon.com/releasenotes/4286407650196705 [1]. > > Can you please also provide more details - what kind of issues exactly are > you encountering? Are any exceptions thrown and if so, which? > > And as always, patches are welcome :) > > On Mon, Sep 9, 2013 at 11:19 PM, Markos Gogoulos <[email protected]> wrote: > >> Hi all, I was trying to launch new instances through libcloud and the ec2 driver and had issues with functions ex_authorize_security_group_permissive and ex_authorize_security_group that allow specific traffic to a security group. This was due to the fact that the API has changed for VPC accounts and new accounts in ec2 are launched with VPC by default. Has anyone experience with this? I can make a pull request and start working on it. Cheers, Markos Links: ------ [1] http://aws.amazon.com/releasenotes/4286407650196705
