Skip to content

C
configuration
Commit 26c65609 by Sef Kloninger
Options

README: reflect general jumpbox ssh config

parent 778f0d44
Showing with 15 additions and 17 deletions
README.md
...@@ -173,32 +173,33 @@ If that works fine, then you can add an export of PYTHONPATH to ...@@ -173,32 +173,33 @@ If that works fine, then you can add an export of PYTHONPATH to
Because the reference architecture makes use of an Amazon VPC, you will not be able Because the reference architecture makes use of an Amazon VPC, you will not be able
to address the hosts in the private subnets directly. However, you can easily set to address the hosts in the private subnets directly. However, you can easily set
up a transparent "jumpbox" so that for all hosts in your vpc, connections are up a transparent "jumpbox" so that for all hosts in your vpc, connections are
tunneled tunneled.
Add something like the following to your `~/.ssh/config` file. Add something like the following to your `~/.ssh/config` file.
``` ```
Host vpc-00000000-jumpbox Host *.us-west-1.compute-internal
HostName 54.236.224.226 ProxyCommand ssh -W %h:%p vpc-00000000-jumpbox
IdentityFile /path/to/aws/key.pem IdentityFile /path/to/aws/key.pem
ForwardAgent yes ForwardAgent yes
User ubuntu User ubuntu
Host 10.0.10.1 Host vpc-00000000-jumpbox
ProxyCommand ssh -W %h:%p vpc-00000000-jumpbox HostName 54.236.224.226
ForwardAgent yes
HostName 10.0.10.242
IdentityFile /path/to/aws/key.pem IdentityFile /path/to/aws/key.pem
ForwardAgent yes
User ubuntu User ubuntu
...
``` ```
You will need a host entry for each server that ansible will configure.
Test this by typing `ssh 10.0.10.1`, use a hostname the exists in This assumes that you only have one VPC in the ```us-west-1``` region
your environment. If things are configured correctly you will ssh that you're trying to ssh into. Internal DNS names aren't qualified
to 10.0.10.1, jumping transparently via your basion host. any further than that, so to support multiple VPC's you'd have to get
creative with subnets, for example ip-10-1 and ip-10-2...
Test this by typing `ssh ip-10-0-10-1.us-west-1.compute.internal`,
(of coruse using a hostname exists in your environment.) If things
are configured correctly you will ssh to 10.0.10.1, jumping
transparently via your basion host.
Assuming that the edxapp_stage.yml playbook targets hosts in your vpc Assuming that the edxapp_stage.yml playbook targets hosts in your vpc
for which there are entiries in your `.ssh/config`, do the for which there are entiries in your `.ssh/config`, do the
...@@ -208,9 +209,6 @@ following to run your playbook. ...@@ -208,9 +209,6 @@ following to run your playbook.
cd playbooks cd playbooks
ansible-playbook -v --user=ubuntu edxapp_stage.yml -i ./ec2.py -c ssh ansible-playbook -v --user=ubuntu edxapp_stage.yml -i ./ec2.py -c ssh
``` ```
We are in the process of writing utility scripts to generate this config,
but for the moment it is a manual process.
*Note: this assumes the group used for the edx stack was "edxapp_stage"* *Note: this assumes the group used for the edx stack was "edxapp_stage"*
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment