Make "shipper" SSH key

[mrdavidlaing]

And link into the Cloudformation cluster config

[mrdavidlaing]

$ ssh-keygen -t rsa -C "subobot+logsearch-ppe-shipper@labs.cityindex.com"
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/mrdavidlaing/.ssh/id_rsa): /Users/mrdavidlaing/.ssh/logsearch-ppe-shipper.pem
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /Users/mrdavidlaing/.ssh/logsearch-ppe-shipper.pem.
Your public key has been saved in /Users/mrdavidlaing/.ssh/logsearch-ppe-shipper.pem.pub.
The key fingerprint is:
ab:5b:34:78:b0:ff:5a:95:8d:17:ca:8a:7c:25:fa:06 subobot+logsearch-ppe-shipper@labs.cityindex.com
The key's randomart image is:
+--[ RSA 2048]----+
|                 |
|                 |
|      .       .  |
|       +   . = . |
|      o S . B o  |
|       =E= = .   |
|        B.+      |
|       o =.      |
|      o..oo      |
+-----------------+

$ cat /Users/mrdavidlaing/.ssh/logsearch-ppe-shipper.pem.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDVUZ1BWZzwaRZF7gTduFJPOdUak5PhfhQyVVb7zr6IPNd+qK3DrWHitp7dgJ/2Xp4+KQ3G9og/WqVT0xBqHo+B9Jl2RqVKvIAmu9zp4H99FGKpQjsBxotwGvR9rRQxGmCmTWffogRKVcUtufCl6MhB0CIqeLtutx1cobjIfed34Asd2HqSEALz0CbxXX90T7xR+vU2W7f0QabT+Yc8CoyZ8hHSe6zQklOr2AzRZsB3WdglbncNuzfl06ZPY1+7Yvc3XgQHl0Gg1SO67vqAPpNy94VGRCAMVOaFDhOJNl6VwDhKrjB4YPwUNl1KH9qIiReuDmCzy1U2fVxGXTPqE2En subobot+logsearch-ppe-shipper@labs.cityindex.com

[mrdavidlaing]

@dpb587 could you:

(a) double check that I have added these keys correctly (b) Let me know when the new shipper key has been added to the existing logsearch-ppe cluster so I can start using it from the PPE shipper

[sopel]

https://github.com/cityindex/logsearch-on-aws/issues/10 yields the decision to handle the key provisioning differently going forward, which is going to be implemented via #146.

[dpb587]

@mrdavidlaing, you should be able to use the new shipper key at your convenience.

[mrdavidlaing]

Switched