[chef] Re: Re: Re: Re: knife ec2 server create in VPC

[mark bradley < >]

Well, when an instance is created manually (i.e. from the AWS console) it is possible to set the IP address in the VPC so surely it's part of the API to AWS.

On Thu, Jun 7, 2012 at 12:23 AM, Ranjib Dey < " target="_blank"> > wrote:

Im not sure if you can do that. Dhcp option set determines the ip. You can push the ip assignment logic in bootstrap script, may br

On Jun 7, 2012 3:01 AM, "mark bradley" < " target="_blank"> > wrote:

Thanks AJ.

I do have the subnet specified, and it's allocating an IP in that subnet, but I'd like to configure it with a specific IP address. Failing that, I'd like to know the algorithm to make sure that the IP doesn't conflict with instances already in that subnet.

I don't need access to the server from external sources, it's purely an internal server so no EIP is required.

It just seems like it would be a huge oversight not to allow specifying the IP address.

Mark

On Wed, Jun 6, 2012 at 5:21 PM, AJ Christensen < " target="_blank"> > wrote:

you can use -s subnet to specify which subnet the machine should be
launched in. Put it in a subnet with NAT if it needs to get out, or
another subnet & allocate an elastic IP if it needs public tubes.

you could also use ENI and attach EIP to the ENI then programmatically
attach the ENI to the instance as it is launched via CloudFormation
(?)

--AJ

On 7 June 2012 08:39, mark bradley < " target="_blank"> > wrote:
> Hello,
>
> I'm trying to use the above command to build/bootstrap a server in our VPC,
> however I do not see any setting for an IP address.
>
> The instance is, however, created with some IP address.
>
> Is it possible to specify the IP address? If so, how? If not then how are
> the IP addresses allocated?
>
> Thanks,
> Mark