Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I was able to make knife access AWS by following: http://www.agileweboperations.com/amazon-ec2-instances-with-opscode-chef-using-knife

Now, I get a knife command almost working:

$ knife ec2 server create -r "role[base]" -I ami-c1aaabb5  -f t1.micro -S knife -i ~/.ssh/knife.pem --ssh-user ubuntu --region eu-west-1 -Z eu-west-1a
Instance ID: i-xxxxxx
Flavor: m1.small
Image: ami-399ca94d
Region: eu-west-1
Availability Zone: eu-west-1a
Security Groups: default
Tags: {"Name"=>"i-xxxxxx"}
SSH Key: knife

Waiting for server............................
Public DNS Name: ec2-xxxxxx.eu-west-1.compute.amazonaws.com
Public IP Address: yy.yy.yy.yy
Private DNS Name: ip-xxxxxxx.eu-west-1.compute.internal
Private IP Address: zz.zz.zz.zz

Waiting for sshd...................................

But now I get a timeout. Any ideas/suggestions how to create an EC2 instance ready for Chef provisioning?

Thanks!

share|improve this question
1  
Does your default security group permit SSH traffic? –  EEAA Jan 29 '13 at 13:56
    
right! there was the problem. I did allow SSH traffic only for another security group... now, provisioning is working! if you post your answer below, I accept it –  poseid Jan 29 '13 at 15:06
    
Ahh, awesome. I've posted an answer... –  EEAA Jan 29 '13 at 16:35

1 Answer 1

up vote 7 down vote accepted

My guess would be that your default security group is not allowing SSH traffic.

share|improve this answer
1  
@EEAA... thank you very much. this helped just now. :) –  slayedbylucifer Jul 22 '13 at 8:56

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.