From 6089bc44f028f66c6ad227aec1369e46e3cc2b4b Mon Sep 17 00:00:00 2001
From: Charles Hooper <charles.hooper@dotcloud.com>
Date: Tue, 26 Mar 2013 17:40:56 +0000
Subject: [PATCH] Use new AMI that won't cause issues with cloud-init
 apply_creds Upstream-commit: 5cebc226cc0d734936a3d63e10027d46f39e8025
 Component: engine

---
 components/engine/Vagrantfile | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/components/engine/Vagrantfile b/components/engine/Vagrantfile
index 4cf5f0a0e5..36f72b907e 100644
--- a/components/engine/Vagrantfile
+++ b/components/engine/Vagrantfile
@@ -119,8 +119,8 @@ end
     aws.keypair_name = ENV["AWS_KEYPAIR_NAME"]
     aws.ssh_private_key_path = ENV["AWS_SSH_PRIVKEY"]
     aws.region = "us-east-1"
-    aws.ami = "ami-1c1e8075"
-    aws.ssh_username = "vagrant"
+    aws.ami = "ami-4a7de623"
+    aws.ssh_username = "ubuntu"
     aws.instance_type = "t1.micro"
   end
   config.vm.provider :virtualbox do |vb|