You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Andrew Bayer (JIRA)" <ji...@apache.org> on 2013/12/06 22:51:36 UTC

[jira] [Created] (JCLOUDS-394) EC2 Security Group logic won't work in non-default VPC

Andrew Bayer created JCLOUDS-394:
------------------------------------

             Summary: EC2 Security Group logic won't work in non-default VPC
                 Key: JCLOUDS-394
                 URL: https://issues.apache.org/jira/browse/JCLOUDS-394
             Project: jclouds
          Issue Type: Bug
          Components: jclouds-compute
    Affects Versions: 1.6.3
            Reporter: Andrew Bayer
            Priority: Blocker
             Fix For: 1.7.0, 1.6.4


Due to the change EC2 just made such that all new accounts are only in EC2-VPC for security groups, with their own default VPC set up for each account, all of our code that uses group *names* for parameters etc will fail for new accounts. This works (I'm pretty sure) from aws-ec2 where we're specifying groupId instead of groupName in a lot of places (hopefully all?), but I think we need to answer how to deal with this for the EC2 api proper as well.



--
This message was sent by Atlassian JIRA
(v6.1#6144)