Skip to content

Commit c0d2ce1

Browse files
committed
changed default location of tutorial git repo
1 parent 41e9015 commit c0d2ce1

File tree

1 file changed

+8
-10
lines changed

1 file changed

+8
-10
lines changed

Cloud_Setup/JPL_setup_instructions.md

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -37,26 +37,24 @@ JPL does not enable `ssh` access to AWS instances by default, instead preferring
3737
- *Initial set up and download GitHub repository*: Copy the following commands and paste in your SSM window (using shift-insert or right-click then **Paste**):
3838

3939
```
40-
$ cd ~ && sudo dnf update -y && sudo dnf install git -y
41-
$ sudo su jpluser
42-
$ cd ~/
43-
$ mkdir git_repos
44-
$ cd git_repos
45-
$ git clone https://github.com/ECCO-GROUP/ECCO-v4-Python-Tutorial.git
40+
cd ~ && sudo dnf update -y && sudo dnf install git -y
41+
sudo su jpluser
42+
cd ~/
43+
git clone https://github.com/ECCO-GROUP/ECCO-v4-Python-Tutorial.git
4644
```
4745

4846
- *Enable ssh access*: There is a script in the GitHub repository to enable ssh access `sshd_enable.sh`. You want to run it as the *root* user, otherwise you will not have the necessary permissions. Again, copy and paste the following in your SSM window:
4947

5048
```
51-
$ sudo ~/git_repos/ECCO-v4-Python-Tutorial/Cloud_Setup/sshd_enable.sh
49+
sudo ~/ECCO-v4-Python-Tutorial/Cloud_Setup/sshd_enable.sh
5250
```
5351

54-
The script will ask if you want to move the git repo and change its ownership. Answer **Y** and enter **jpluser** for user name.
52+
The script will ask if you want to generate new SSH keys, answer **Y**. Then it will ask if you want to move the git repo and change its ownership. Answer **Y** and enter **jpluser** for user name.
5553

5654
Once the script is completed, you should be able to ssh into your new instance. You can **Terminate** the SSM window. Then from your machine's terminal window, connect to the instance's *private* IPv4 address (given on the AWS instance summary page) with user name **jpluser**. For example, if the key file is `~/.ssh/aws_ec2_jupyter.pem` and the private IPv4 address is 100.104.70.37, then:
5755

5856
```
59-
$ ssh -i "~/.ssh/aws_ec2_jupyter.pem" [email protected] -L 9889:localhost:9889
57+
ssh -i "~/.ssh/aws_ec2_jupyter.pem" [email protected] -L 9889:localhost:9889
6058
```
6159

6260
The `-L` option indicates a tunnel from the local machine's port 9889 to the instance's port 9889; this will be used later to open Jupyterlab through your local machine's web browser.
@@ -80,7 +78,7 @@ Now you need to install software (conda/miniconda/miniforge) to run Python, and
8078
To run `jupyter_env_setup.sh`, copy, paste, and execute the following two commands on the instance:
8179

8280
```
83-
$ sudo chmod 755 ~/git_repos/ECCO-v4-Python-Tutorial/Cloud_Setup/jupyter_env_setup.sh && ~/git_repos/ECCO-v4-Python-Tutorial/Cloud_Setup/jupyter_env_setup.sh
81+
sudo chmod 755 ~/ECCO-v4-Python-Tutorial/Cloud_Setup/jupyter_env_setup.sh && ~/ECCO-v4-Python-Tutorial/Cloud_Setup/jupyter_env_setup.sh
8482
```
8583

8684
The script takes several minutes to run, but it should set up our environment with the packages we need. Now you can return to Step 4 of the [AWS Cloud: getting started](https://ecco-v4-python-tutorial.readthedocs.io/AWS_Cloud_getting_started.html) tutorial.

0 commit comments

Comments
 (0)