Cannot connect to instance about sagemaker-ssh-helper HOT 4 CLOSED

Hi, João.

Thanks for sharing the redacted output. It's still not clear where is the issue.

Could you also check and copy the logs from the /var/log/amazon/ssm/amazon-ssm-agent.log that appear when you run the sm-ssh-ide ssm-agent command?

You can do this by opening and image terminal (the small icon with $_ sign at the toolbar) and copying the log file to the home directory with the following command:

cp /var/log/amazon/ssm/amazon-ssm-agent.log ~

Then you can open this file from a file browser and copy-paste the relevant lines here or download and attach the whole file (if possible).

Regards, Ivan

Hi @ivan-khvostishkov ,

I checked the logs as you suggested and found that there were some AccessDenied errors due to SSM permissions missing in the role that I was using. Added them and it works now, can connect from local to the instance! Thanks for the tips and looking forward to starting using this.

from sagemaker-ssh-helper.

Hi, João.

Thank you for the interest in the SageMaker SSH Helper!

When you run the steps in the notebook, the command sm-ssh-ide ssm-agent connects to the SSM Agent and you should keep it running (do not stop the kernel). To validate that the SageMaker Studio app has connected to SSM, go to the Systems Manager Console > Fleet Manager and check that a new managed node appeared in the list and got the “SSM Agent ping status” as Online.

When it's Online, the command sm-local-ssh-ide <<kernel_gateway_app_name>> should establish a connection successfully.

Hope it helps!

But if it's still doesn't work, please, share the output of the cell with sm-ssh-ide init-ssm command.

Regards,
Ivan

from sagemaker-ssh-helper.

Hi, João.

Thank you for the interest in the SageMaker SSH Helper!

When you run the steps in the notebook, the command sm-ssh-ide ssm-agent connects to the SSM Agent and you should keep it running (do not stop the kernel). To validate that the SageMaker Studio app has connected to SSM, go to the Systems Manager Console > Fleet Manager and check that a new managed node appeared in the list and got the “SSM Agent ping status” as Online.

When it's Online, the command sm-local-ssh-ide <<kernel_gateway_app_name>> should establish a connection successfully.

Hope it helps!

But if it's still doesn't work, please, share the output of the cell with sm-ssh-ide init-ssm command.

Regards, Ivan

Hi Ivan,

Thanks for the quick reply. I checked that after I run sm-ssh-ide ssm-agent the instance does not show up in Fleet Manager.
Please find below the output of sm-ssh-ide init-ssm:

_install_aws_cli
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 45.1M  100 45.1M    0     0   105M      0 --:--:-- --:--:-- --:--:--  104M

if _is_centos; then
  _install_ssm_agent_centos
else
  _install_ssm_agent_ubuntu
fi
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 30.5M  100 30.5M    0     0  92.9M      0 --:--:-- --:--:-- --:--:-- 92.9M

cat >/etc/amazon/ssm/amazon-ssm-agent.json <<EOF
{
    "Profile":{
        "ShareCreds" : true,
        "ShareProfile" : "ssm",
        "ForceUpdateCreds" : false,
        "KeyAutoRotateDays": 0
    }
}
EOF

response=$(aws ssm create-activation \
  --description "Activation for Amazon SageMaker integration with SSH and IDEs" \
  --iam-role "$SSH_SSM_ROLE" \
  --registration-limit 1 \
  --region "$CURRENT_REGION" \
  --tags "$SSH_SSM_TAGS")

if _is_centos; then
  yum install -y jq
fi

acode=$(echo $response | jq --raw-output '.ActivationCode')
aid=$(echo $response | jq --raw-output '.ActivationId')

echo Yes | amazon-ssm-agent -register -id "$aid" -code "$acode" -region "$CURRENT_REGION"
2022/11/04 15:52:39 Found config file at /etc/amazon/ssm/amazon-ssm-agent.json.
2022/11/04 15:52:39 processing appconfig overrides
Found config file at /etc/amazon/ssm/amazon-ssm-agent.json.
processing appconfig overrides

# See https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-getting-started-ssm-user-permissions.html
if _is_centos; then
  yum install -y sudo
else
  apt-get install -y sudo
fi
debconf: delaying package configuration, since apt-utils is not installed
echo "ssm-user ALL=(ALL) NOPASSWD:ALL" > /etc/sudoers.d/ssm-agent-users
```

from sagemaker-ssh-helper.

Hi, João.

Thanks for sharing the redacted output. It's still not clear where is the issue.

Could you also check and copy the logs from the /var/log/amazon/ssm/amazon-ssm-agent.log that appear when you run the sm-ssh-ide ssm-agent command?

You can do this by opening and image terminal (the small icon with $_ sign at the toolbar) and copying the log file to the home directory with the following command:

cp /var/log/amazon/ssm/amazon-ssm-agent.log ~

Then you can open this file from a file browser and copy-paste the relevant lines here or download and attach the whole file (if possible).

Regards,
Ivan

from sagemaker-ssh-helper.