aws-ssh-resolver 0.0.2 → 0.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: f935d670a01180e51698c25ea3ca209884f43556
-  data.tar.gz: ee1f14a33bcbe6b9ead7babf3fd625d96f3de9c0
+  metadata.gz: 48b42c80586cba35d4917fba72f764eba15bdb57
+  data.tar.gz: d7fe8b98efb41cd92e415a32e601534e134eafd5
 SHA512:
-  metadata.gz: 02580ee44766981ab87b40e4f5f8bdac0cd1ab5e0e1ce3082f393272fac7b144bfa4f9b3c568834d6bb66b40b54f20c698cce7a2b162e737c516bd213fddd5fc
-  data.tar.gz: 013f95baba3d2fef334144d5995bdc373992b9e6ece6e88287ca2ee2937047c2fc70128ead909c8e50c3e2dedf34f0f2e70a819fa3e0aadad6b6c5d9c37933c9
+  metadata.gz: 0ea88291e226d0cd730e7f8ff6a497a97734cfdf4302a7b143708e7095f2be6a8116bb00461f2f457be9f53534b1fda40c14cd6ab812fd78c5b9d77e9b574df0
+  data.tar.gz: d7d6ea498c200312ac63aac4fbd0fcfc5e21c796916472e2925181fcd996070715984d8f3cc901848afa686ac0cd93ba208c0b8fe3043ebb63c55b497ad6017f

data/README.md

@@ -1,35 +1,21 @@
-# aws-ssh-resolver - Resolve AWS EC2 HostNames for OpenSSH configuration - $Release:0.0.2$
+# aws-ssh-resolver - Resolve AWS EC2 HostNames for OpenSSH configuration - $Release:0.0.3$
 
 `aws-ssh-resolver` keeps AWS EC2 HostNames in OpenSSH configuration
-file in sync with Amazon cloud making it easier for a user to use
-OpenSSH, and related tools, on Amazon Platform.
+file in sync with Amazon cloud making it easier for to use OpenSSH,
+and related tools, on Amazon Platform.
 
 ## The Problem
 
-Every EC2 instance on Amazon platform has a Private IP address, and a
-DNS hostname resolving to this address. Private IP cannot be reached
-directly from the Internet, and the Private DNS name can be resolved
-only on the network that the instance is in. An instance may be
-assigned a Public IP Address, and corresponding Public DNS name.  The
-Public IP is accessible from the Internet, and the Public DNS name is
-resolvable outside the network of the instance.  Public IPs come from
-Amazon's pool of public IP address, and an instance may not reuse the
-IP address, once it is released. For example, stopping, or
-terminating, an instance releases the Public IP Address. See Amazon
-[documentation](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html)
-for more details.
-
-
-Amazon EC2 Instance IP Addressing presents several challenges for SSH
-usage, or any SSH related tool e.g.
-[ansible](http://www.ansible.com/home),
+[Amazon EC2 Instance IP Addressing](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html)
+sets several challenges for SSH usage, and for any tool using SSH
+connections e.g.  [ansible](http://www.ansible.com/home),
 [fabric](http://www.fabfile.org/),
 [serverspec](http://serverspec.org/) etc.
 
-* Public DNS Name encodes the Public IP Address. Each time an instance
-  is assigned a new IP address, it also gets a new Public DNS name, In
-  essence this means that the task of managing DNS names becomes
-  comparable to the task of managing IP addresses.
+* Amazon Public DNS Names encode Public IP Addresses. Each time an
+  instance is assigned a new IP address, it also gets a new Public DNS
+  name. In essence this means that the task of managing DNS names
+  becomes comparable to the task of managing IP addresses.
 
 * Using an IP address to contact an instance is complicated, because
   Public IP Address, once released, cannot be reused. Using fixed IP
@@ -62,7 +48,10 @@ addresses the challenges above
     configuration in OpenSSH allows users to create a transparent
     multihop SSH connection to EC2 instances with Private IP Address
     only
-	
+
+For more background information, see
+[blog post](https://jarjuk.wordpress.com/2015/09/08/using-openssh-on-aws-platform/#more-273https://jarjuk.wordpress.com/2015/09/08/using-openssh-on-aws-platform/#more-273).
+
 ## Usage
 
 ### Installation
@@ -84,11 +73,10 @@ file `ssh/config.aws` with any fixed configuration.  Running
 **aws-ssh-resolver** updates this file, but does not interfere with
 the content user has entered.
 
-**Notice**: If `ssh/config.aws` -file does not exist, the first
-**aws-ssh-resolver** run creates the initial version of
-`ssh/config.aws` automatically using `ssh/config.init`. This avoids
-the need to check in the mutable `ssh/config.aws` into a version
-nncontrol system.
+**Notice**: The first **aws-ssh-resolver** run creates the initial
+version of `ssh/config.aws` automatically using `ssh/config.init`, if
+`ssh/config.aws` -file does not exist, . This avoids the need to check
+in the mutable `ssh/config.aws` into a version control system.
 
 ### Update OpenSSH Configuration file
 
@@ -98,7 +86,7 @@ command:
 
 	aws ec2 describe-instances |  bundle exec aws-ssh-resolver.rb resolve
 
-The command extract EC2 Tag/DNS information, and writes
+The command extracts EC2 Tag/DNS information, and writes
 `host`/`HostName` configuration entries in `ssh/config.aws` -file.  In
 this file `host` value is taken from `Name` tag on an EC2 instance,
 and `HostName` value is taken from `PublicDnsName` on an EC2
@@ -207,7 +195,7 @@ OpenSSH uses the proxy definition to access it.
 
 ### Using OpenSSH Configuration to Access ASW Instances
 
-The configuration in `ssh/configaws` allows us to use tag name
+The configuration in `ssh/config.aws` allows us to use tag name
 `myFront1` to make a SSH connection to machine with the DNS name
 `c2-52-19-117-227.eu-west-1.compute.amazonaws.com` simply with command
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-ssh-resolver
 version: !ruby/object:Gem::Version
-  version: 0.0.2
+  version: 0.0.3
 platform: ruby
 authors:
 - jarjuk
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-09-07 00:00:00.000000000 Z
+date: 2015-09-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: thor