From 20e7ec6a282c44e4673e102d4456cb3543cc04ce Mon Sep 17 00:00:00 2001 From: Stan Lemon Date: Wed, 8 May 2013 09:03:40 -0400 Subject: [PATCH] Removed reload from the sync folder section since it is not implemented and added notes on how to get this working with Amazon Linux AMIs. --- README.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 4637fd05..9a48eba4 100644 --- a/README.md +++ b/README.md @@ -166,13 +166,25 @@ the AWS machine. ## Synced Folders There is minimal support for synced folders. Upon `vagrant up`, -`vagrant reload`, and `vagrant provision`, the AWS provider will use + and `vagrant provision`, the AWS provider will use `rsync` (if available) to uni-directionally sync the folder to the remote machine over SSH. This is good enough for all built-in Vagrant provisioners (shell, chef, and puppet) to work! +## Amazon Linux AMI's + +[Amazon Linux AMIs](http://aws.amazon.com/amazon-linux-ami/) are set +to require tty when sudo'ing, which causes problems when Vagrant tries +to do things like setup the rsync folder. In order to get around this +you can send aws user_data to populate the cloud init config and change this +for the ec2-user when the instance is created: + +```ruby +aws.user_data = "#!/bin/bash\necho 'Defaults:ec2-user !requiretty' > /etc/sudoers.d/999-vagrant-cloud-init-requiretty && chmod 440 /etc/sudoers.d/999-vagrant-cloud-init-requiretty\nyum install -y puppet\n" +``` + ## Other Examples ### Tags