Open madhuksridhar opened 5 months ago
I am unable to connect via ssh. My attempt to connect times out, but I suspect that's because my ip address isn't in the allowed ranges that I see configured for inbound on port 22. I suspect these are MCP ranges:
Connecting to the VPN didn't help. However, I was able to connect via Session Manager in the browser (via AWS Console).
The instructions for setting up prerequisites are a bit off, so I'm adding notes here for adjustment. For using AWS Session Manager:
sh
(at least when connecting via Session Manager), but bash
should be used, so after connecting, run bash
to enter a Bash shell.curl -o- https://raw.githubusercontent.com/creationix/nvm/master/install.sh | bash
~/.profile
, but that file won't get sourced when switching from sh
to bash
, so they won't have any effect (i.e., nvm
won't be found). Move the 2 lines from the end of ~/.profile
to the end of ~/.bashrc
exit
then bash
to make nvm
available.npm
because installing node
via nvm
automatically installs npm
as well, as follows: nvm install --lts
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
sudo apt-get update
sudo apt-get install -y docker-ce
docker --version
sudo usermod -aG docker $(whoami) # Automatically run `docker` as `sudo docker` for current user
curl -fsSL https://get.pulumi.com | sh
~/.bashrc
:
export PATH=${PATH}:${HOME}/.pulumi/bin
exit
then bash
pulumi version
to confirm pulumi
can be foundThis allowed me to get all prereqs installed on the instance for user ssm-user
.
We may want to move Pulumi from /home/ssm-user/.pulumi
to /usr/local/pulumi
and add symlink from /usr/local/bin/pulumi
to /usr/local/pulumi/bin/pulumi
to allow other ssh users run pulumi commands (likely user ubuntu
, in addition to ssm-user
).
Compiled some notes about connecting to Pulumi stack here. Need to tagup with @chuckwondo to discuss further.
Background
This EC2 instance is used to manage/deploy LPDAAC reconciliation workflow. We need to migrate this to a new CSET instance on MCP and remove the old EC2 instance.
Old instance name: HLS_reconciliation New instance name: HLS_reconciliation_CSET_2023 LPDAAC Reconciliation repo: hls-lpdaac-orchestration
Tasks