diff options
author | Matt Cowger <matt@cowger.us> | 2015-06-29 12:05:06 -0700 |
---|---|---|
committer | Matt Cowger <matt@cowger.us> | 2015-06-29 12:05:06 -0700 |
commit | 918ef211398a6a7ac153f213006386ec385fbc84 (patch) | |
tree | 8dc20476d43b86a0a3f70af53d3e41a78235f612 | |
parent | accd98845aac3e271295e3115501b25e6d72b114 (diff) | |
download | openshift-918ef211398a6a7ac153f213006386ec385fbc84.tar.gz openshift-918ef211398a6a7ac153f213006386ec385fbc84.tar.bz2 openshift-918ef211398a6a7ac153f213006386ec385fbc84.tar.xz openshift-918ef211398a6a7ac153f213006386ec385fbc84.zip |
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. |