diff options
| author | Thomas Wiest <twiest@users.noreply.github.com> | 2015-07-06 13:51:03 -0400 |
|---|---|---|
| committer | Thomas Wiest <twiest@users.noreply.github.com> | 2015-07-06 13:51:03 -0400 |
| commit | 6a54f64f34ec13a69fae9d4e5527b0fb95a067ab (patch) | |
| tree | 6cee47844a0ed9a21efd765f145c8f788d69fbb8 | |
| parent | 6ae88062163562c8b67090c0522596a2c0c9fd51 (diff) | |
| parent | 918ef211398a6a7ac153f213006386ec385fbc84 (diff) | |
Merge pull request #316 from mcowger/patch-1
Fix the formatting for the SSH config file
| -rw-r--r-- | README_AWS.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/README_AWS.md b/README_AWS.md index 7f4b1832b..5db36b5cb 100644 --- a/README_AWS.md +++ b/README_AWS.md @@ -27,10 +27,10 @@ In case of a cluster creation, or any other case where you don't know the machin to setup a private key file to allow ansible to connect to the created hosts. To do so, add the the following entry to your $HOME/.ssh/config file and make it point to the private key file which allows you to login on AWS. -''' +``` Host *.compute-1.amazonaws.com PrivateKey $HOME/.ssh/my_private_key.pem -''' +``` Alternatively, you can configure your ssh-agent to hold the credentials to connect to your AWS instances. |