You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jclouds.apache.org by Duncan Johnston Watt <du...@cloudsoftcorp.com> on 2013/12/06 17:16:44 UTC
EC2-CLASSIC vs EC2-VPC
Apologies if this has been covered but as of Weds AWS accounts are EC2-VPC
only.
If you created your AWS account after 2013-12-04, it supports only EC2-VPC.
In this case, we create a default VPC for you in each AWS region.
Therefore, unless you create a nondefault VPC and specify it when you
launch an instance, we launch your instances into your default VPC.
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/default-vpc.html
See also
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html
Is jclouds EC2 support compromised by this?
Best
--
Duncan Johnston-Watt
CEO | Cloudsoft Corporation
Twitter | @duncanjw
Mobile | +44 777 190 2653
Skype | duncan_johnstonwatt
Linkedin | www.linkedin.com/in/duncanjohnstonwatt
Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
This e-mail message is confidential and for use by the addressee only. If
the message is received by anyone other than the addressee, please return
the message to the sender by replying to it and then delete the message
from your computer. Internet e-mails are not necessarily secure. Cloudsoft
Corporation Limited does not accept responsibility for changes made to this
message after it was sent.
Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the
onward transmission, opening or use of this message and any attachments
will not adversely affect its systems or data. No responsibility is
accepted by Cloudsoft Corporation Limited in this regard and the recipient
should carry out such virus and other checks as it considers appropriate.
Re: EC2-CLASSIC vs EC2-VPC
Posted by Jai M <ja...@gmail.com>.
Just wanted to add to this thread.
We have been using jclouds for EC2 and did not have issues with the
"default VPC" during instance creation (createNode api). The same code
works without any issues in both older and newer accounts.
On Fri, Dec 6, 2013 at 1:57 PM, Andrew Bayer <an...@gmail.com> wrote:
> Ok, I'm fairly sure the issue only shows up when you use the ec2 API
> directly. When you go with aws-ec2, groupId is used instead of groupName and
> things work. That said, I've opened
> https://issues.apache.org/jira/browse/JCLOUDS-394 - I'd like to see us
> figure out exactly what to do with the ec2 API's security group handling
> before we push 1.7.0.
>
> A.
>
>
> On Fri, Dec 6, 2013 at 1:18 PM, Andrew Bayer <an...@gmail.com> wrote:
>>
>> Ah, there is an issue - the security group name vs ID thing. I'll see what
>> I can figure out about fixing that.
>>
>> A.
>>
>>
>> On Fri, Dec 6, 2013 at 1:05 PM, Andrew Bayer <an...@gmail.com>
>> wrote:
>>>
>>> I believe they should work without issue, but I'll need to double-check
>>> to be safe. Will do that this weekend.
>>>
>>> A.
>>>
>>>
>>> On Fri, Dec 6, 2013 at 8:32 AM, Andrew Phillips <an...@apache.org>
>>> wrote:
>>>>>
>>>>> 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
>>>
>>>
>>
>
Re: EC2-CLASSIC vs EC2-VPC
Posted by Jai M <ja...@gmail.com>.
Just wanted to add to this thread.
We have been using jclouds for EC2 and did not have issues with the
"default VPC" during instance creation (createNode api). The same code
works without any issues in both older and newer accounts.
On Fri, Dec 6, 2013 at 1:57 PM, Andrew Bayer <an...@gmail.com> wrote:
> Ok, I'm fairly sure the issue only shows up when you use the ec2 API
> directly. When you go with aws-ec2, groupId is used instead of groupName and
> things work. That said, I've opened
> https://issues.apache.org/jira/browse/JCLOUDS-394 - I'd like to see us
> figure out exactly what to do with the ec2 API's security group handling
> before we push 1.7.0.
>
> A.
>
>
> On Fri, Dec 6, 2013 at 1:18 PM, Andrew Bayer <an...@gmail.com> wrote:
>>
>> Ah, there is an issue - the security group name vs ID thing. I'll see what
>> I can figure out about fixing that.
>>
>> A.
>>
>>
>> On Fri, Dec 6, 2013 at 1:05 PM, Andrew Bayer <an...@gmail.com>
>> wrote:
>>>
>>> I believe they should work without issue, but I'll need to double-check
>>> to be safe. Will do that this weekend.
>>>
>>> A.
>>>
>>>
>>> On Fri, Dec 6, 2013 at 8:32 AM, Andrew Phillips <an...@apache.org>
>>> wrote:
>>>>>
>>>>> 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
>>>
>>>
>>
>
Re: EC2-CLASSIC vs EC2-VPC
Posted by Andrew Bayer <an...@gmail.com>.
Ok, I'm fairly sure the issue only shows up when you use the ec2 API
directly. When you go with aws-ec2, groupId is used instead of groupName
and things work. That said, I've opened
https://issues.apache.org/jira/browse/JCLOUDS-394 - I'd like to see us
figure out exactly what to do with the ec2 API's security group handling
before we push 1.7.0.
A.
On Fri, Dec 6, 2013 at 1:18 PM, Andrew Bayer <an...@gmail.com> wrote:
> Ah, there is an issue - the security group name vs ID thing. I'll see what
> I can figure out about fixing that.
>
> A.
>
>
> On Fri, Dec 6, 2013 at 1:05 PM, Andrew Bayer <an...@gmail.com>wrote:
>
>> I believe they should work without issue, but I'll need to double-check
>> to be safe. Will do that this weekend.
>>
>> A.
>>
>>
>> On Fri, Dec 6, 2013 at 8:32 AM, Andrew Phillips <an...@apache.org>wrote:
>>
>>> 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
>>>
>>
>>
>
Re: EC2-CLASSIC vs EC2-VPC
Posted by Andrew Bayer <an...@gmail.com>.
Ok, I'm fairly sure the issue only shows up when you use the ec2 API
directly. When you go with aws-ec2, groupId is used instead of groupName
and things work. That said, I've opened
https://issues.apache.org/jira/browse/JCLOUDS-394 - I'd like to see us
figure out exactly what to do with the ec2 API's security group handling
before we push 1.7.0.
A.
On Fri, Dec 6, 2013 at 1:18 PM, Andrew Bayer <an...@gmail.com> wrote:
> Ah, there is an issue - the security group name vs ID thing. I'll see what
> I can figure out about fixing that.
>
> A.
>
>
> On Fri, Dec 6, 2013 at 1:05 PM, Andrew Bayer <an...@gmail.com>wrote:
>
>> I believe they should work without issue, but I'll need to double-check
>> to be safe. Will do that this weekend.
>>
>> A.
>>
>>
>> On Fri, Dec 6, 2013 at 8:32 AM, Andrew Phillips <an...@apache.org>wrote:
>>
>>> 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
>>>
>>
>>
>
Re: EC2-CLASSIC vs EC2-VPC
Posted by Andrew Bayer <an...@gmail.com>.
Ah, there is an issue - the security group name vs ID thing. I'll see what
I can figure out about fixing that.
A.
On Fri, Dec 6, 2013 at 1:05 PM, Andrew Bayer <an...@gmail.com> wrote:
> I believe they should work without issue, but I'll need to double-check to
> be safe. Will do that this weekend.
>
> A.
>
>
> On Fri, Dec 6, 2013 at 8:32 AM, Andrew Phillips <an...@apache.org>wrote:
>
>> 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
>>
>
>
Re: EC2-CLASSIC vs EC2-VPC
Posted by Andrew Bayer <an...@gmail.com>.
I believe they should work without issue, but I'll need to double-check to
be safe. Will do that this weekend.
A.
On Fri, Dec 6, 2013 at 8:32 AM, Andrew Phillips <an...@apache.org> wrote:
> 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
>
Re: EC2-CLASSIC vs EC2-VPC
Posted by Andrew Phillips <an...@apache.org>.
> 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