From owner-freebsd-questions@FreeBSD.ORG Tue Dec 10 13:27:38 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1E51EFDB for ; Tue, 10 Dec 2013 13:27:38 +0000 (UTC) Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AC1571AF1 for ; Tue, 10 Dec 2013 13:27:37 +0000 (UTC) Received: by mail-wg0-f49.google.com with SMTP id x12so4819759wgg.28 for ; Tue, 10 Dec 2013 05:27:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=LpDXVCI3i9IVyoieVFUGFwrOIce49e2B5Xn07E8JPSA=; b=uzEFHLxvbRpdyTBVn0ii2VcbDFYpOwKnQGZQH2kj/8LjGcB9plu+v8tERfIt27MNRe MguNR0La/fKLU/T4cer+8POFmge+hr4vwh2HftIuyKckrQIyaqlbBzhJTIU5kxtwsjlV XBbHsSwoljtMVNaGTVrTo/3LjBHfJD2tubSyI764W5Js25p0upUYHslsb+nj4v0Mom9E 1jY55ay7BwEzgWGwv813HBwyyLVeMNhl/QA8xGDoZolLcYYTm2QMLfJNeDL3eTLcoFHx /vxyBpNaholV558bgMslBipe4uzSXwV+EqbLxR/rcGyA0AVA6kYdL8/0kzg/zcwmXdYp 6a5w== MIME-Version: 1.0 X-Received: by 10.180.109.201 with SMTP id hu9mr19086940wib.59.1386682055804; Tue, 10 Dec 2013 05:27:35 -0800 (PST) Received: by 10.216.160.79 with HTTP; Tue, 10 Dec 2013 05:27:35 -0800 (PST) In-Reply-To: References: Date: Tue, 10 Dec 2013 07:27:35 -0600 Message-ID: Subject: Re: FreeBSD on EC2 From: David Noel To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: David.I.Noel@gmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Dec 2013 13:27:38 -0000 OK, I just heard back from Colin with the solution. Apparently Amazon scraps their default to allow policy when you spin up Windows instances so you have to explicitly allow SSH connections in the security group settings. On 12/10/13, David Noel wrote: > No luck with "ami-12576757". Am I the only one having trouble with > EC2? It's free to launch a micro instance. Can anyone else try this > and verify that the AMI's aren't working? > > On 12/9/13, David Noel wrote: >>> On 12/7/13, David Noel wrote: >>>> I started a 10-BETA4 ami on us-west and tried ssh'ing in but had no >>>> success. "Operation timed out" is the output. Does anyone know why >>>> this might be? The default security group policies default to allowing >>>> connections on port 22 from any IP address so I'm confused why ssh >>>> isn't working. >>>> >>> On 12/8/13, David Noel wrote: >>> Forgot to update firewall rules to allow outbound ssh. That should fix >>> it. >> >> No, that's not it. Something else is wrong. I spun up "ami-2ebfda1e" >> on a free micro instance and tried to ssh in. No luck. I spun up a >> RHEL instance and ssh'd in just fine. Is anyone able to log in to the >> FreeBSD ami's? If so, which one/s did you use? >> >