mirror of
https://github.com/bigchaindb/bigchaindb.git
synced 2024-10-13 13:34:05 +00:00
Docs on using special SSH keypair with ACS/Kubernetes
This commit is contained in:
@@ -42,23 +42,10 @@ This writes two files: `~/.aws/credentials` and `~/.aws/config`. AWS tools and p
|
||||
|
||||
Eventually, you'll have one or more instances (virtual machines) running on AWS and you'll want to SSH to them. To do that, you need a public/private key pair. The public key will be sent to AWS, and you can tell AWS to put it in any instances you provision there. You'll keep the private key on your local workstation.
|
||||
|
||||
First you need to make up a key name. Some ideas:
|
||||
See the [page about how to generate a key pair for SSH](generate-key-pair-for-ssh.html).
|
||||
|
||||
* `bcdb-troy-1`
|
||||
* `bigchaindb-7`
|
||||
* `bcdb-jupiter`
|
||||
|
||||
If you already have key pairs on AWS (Amazon EC2), you have to pick a name that's not already being used.
|
||||
Below, replace every instance of `<key-name>` with your actual key name.
|
||||
To generate a public/private RSA key pair with that name:
|
||||
```text
|
||||
ssh-keygen -t rsa -C "<key-name>" -f ~/.ssh/<key-name>
|
||||
```
|
||||
|
||||
It will ask you for a passphrase. You can use whatever passphrase you like, but don't lose it. Two keys (files) will be created in `~/.ssh/`:
|
||||
|
||||
1. `~/.ssh/<key-name>.pub` is the public key
|
||||
2. `~/.ssh/<key-name>` is the private key
|
||||
## Send the Public Key to AWS
|
||||
|
||||
To send the public key to AWS, use the AWS Command-Line Interface:
|
||||
```text
|
||||
|
||||
34
docs/server/source/appendices/generate-key-pair-for-ssh.md
Normal file
34
docs/server/source/appendices/generate-key-pair-for-ssh.md
Normal file
@@ -0,0 +1,34 @@
|
||||
# Generate a Key Pair for SSH
|
||||
|
||||
This page describes how to use `ssh-keygen`
|
||||
to generate a public/private RSA key pair
|
||||
that can be used with SSH.
|
||||
(Note: `ssh-keygen` is found on most Linux and Unix-like
|
||||
operating systems; if you're using Windows,
|
||||
then you'll have to use another tool,
|
||||
such as PuTTYgen.)
|
||||
|
||||
By convention, SSH key pairs get stored in the `~/.ssh/` directory.
|
||||
Check what keys you already have there:
|
||||
```text
|
||||
ls -1 ~/.ssh/
|
||||
```
|
||||
|
||||
Next, make up a new key pair name (called `<name>` below).
|
||||
Here are some ideas:
|
||||
|
||||
* `aws-bdb-2`
|
||||
* `tim-bdb-azure`
|
||||
* `chris-bcdb-key`
|
||||
|
||||
Next, generate a public/private RSA key pair with that name:
|
||||
```text
|
||||
ssh-keygen -t rsa -C "<name>" -f ~/.ssh/<name>
|
||||
```
|
||||
|
||||
It will ask you for a passphrase.
|
||||
You can use whatever passphrase you like, but don't lose it.
|
||||
Two keys (files) will be created in `~/.ssh/`:
|
||||
|
||||
1. `~/.ssh/<name>.pub` is the public key
|
||||
2. `~/.ssh/<name>` is the private key
|
||||
@@ -17,6 +17,7 @@ Appendices
|
||||
pipelines
|
||||
backend
|
||||
aws-setup
|
||||
generate-key-pair-for-ssh
|
||||
firewall-notes
|
||||
ntp-notes
|
||||
example-rethinkdb-storage-setups
|
||||
|
||||
Reference in New Issue
Block a user