Skip to content
This repository has been archived by the owner on Feb 11, 2022. It is now read-only.

README improvements #70

Closed
wants to merge 1 commit into from
Closed

README improvements #70

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down