-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create documentation for NOS Sandbox login steps #85
Comments
@ZacharyWills I obscured the IP addresses and didn't put a screenshot of the Bastion server screen because I wasn't sure if we should show the IP addresses in here. I can change it if you think it's though. |
Perhaps this should be moved to be a permanent document as a README or SOP. |
@zachary Wills - NOAA Affiliate ***@***.***> I put the
information in there for you. It does scream SOP to me when I look at it
too. What do you think? Should we move it?
Michael
…On Mon, May 13, 2024 at 10:20 AM Chris Paternostro ***@***.***> wrote:
Perhaps this should be moved to be a permanent document as a README or SOP.
—
Reply to this email directly, view it on GitHub
<#85 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR7UUIFAGZK5IGLDVEGOIXTZCDD25AVCNFSM6AAAAABG3POR7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBXG4YTIMBYGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
From Jiantao Xu in CO-OPS related to accessing through the CO-OPS system For Windows with Tectia:
For Linux/Unix (For CO-OPS modeling team, this will be ofswork-east1):
|
This is a list of the steps I use for logging into the sandbox.
*Note: if you are working in the office you might not need to connect to the VPN to access the Bastion server
Connect to the VPN
SSH into the Bastion server
Using Putty:
SSH into the head node
ssh -i ~/.ssh/ioos.pem ec2-user@...
Do science
Email from Arnold about accounts:
Welcome IOOS Bastion User,
I hope this message finds you well. I am writing to inform you that you have been granted access to the IOOS Bastion (IP: ...**) in the Coastal Modeling Sandbox. This access is an important part of our ongoing projects and collaborations.
Linux Username: Please note that your Linux username for accessing the Bastion is the same as the name of the Google Drive folder name being shared with you. It follows the format of your first and last name in lowercase, separated by a dot (e.g., john.doe).
Access Requirements:
Connection to the ERAV VPN is mandatory before accessing the Bastion. This can be achieved using the Cisco AnyConnect client.
Your SSH keys (id_rsa and id_rsa.pub) have been provided in the Google Drive folder specifically shared with your email.
Instructions for Using SSH Keys:
Windows Users:
Windows Native SSH Client:
Download the
id_rsa
andid_rsa.pub
files from your Google Drive folder.Move these files to the
.ssh
directory located in your user folder (e.g., C:\Users[YourUsername].ssh). If the directory does not exist, create it.Right-click on the Start button and select 'Windows PowerShell' or 'Command Prompt'.
To ensure the SSH client can use your private key, set the correct permissions: Execute
icacls .ssh\id_rsa /inheritance:r /grant:r "%username%:r"
within the PowerShell or Command Prompt.To connect to the Bastion, use the following command:
ssh [your.username]@[***.**.**.***](http://***.**.**.***/)
PuTTY Users:
Download the
id_rsa
file from your Google Drive folder.Download and open PuTTYgen (available from the PuTTY download page).
In PuTTYgen, click 'Load' and select the
id_rsa
file. It will prompt that it successfully imported the foreign key.Click 'Save private key' to save the key in PuTTY’s format (.ppk file). You can save it with the same name for consistency.
Open PuTTY, enter the Host Name
***.**.**.***
and ensure the Port is set to22
.Go to Connection > SSH > Auth. Under "Private key file for authentication:", browse and select your .ppk file.
Go back to the Session page, enter a name under 'Saved Sessions', and click 'Save' to save these settings.
Click 'Open' to initiate the connection. Enter your Linux username when prompted.
Important: Please handle your SSH keys with utmost care and never share them with others. These keys provide secure, encrypted access to critical systems.
Should you have any questions or require further assistance, please do not hesitate to reach out.
The text was updated successfully, but these errors were encountered: