SSH or RDP to a Deadline Cloud worker through Session Manager
The
ssh_to_smf
The job follows this sequence:
-
The submit script creates a one-time SSM hybrid activation by calling
aws ssm create-activation. -
The Deadline Cloud job runs on a worker, registers the worker as a managed node, and prints the
mi-*managed node ID to the job log. -
You connect with
aws ssm start-session --target mi-.XXXXXXXXX -
After the configured session duration, the job deregisters the node and cleans up.
To set up SSH access for one-time per account and Region
-
Create an IAM role named
SSMServiceRolewith the SSM service principal trust and theAmazonSSMManagedInstanceCoremanaged policy attached. -
Enable the advanced-instances tier:
aws ssm update-service-setting \ --setting-id "arn:aws:ssm:region:account-id:servicesetting/ssm/managed-instance/activation-tier" \ --setting-value "advanced" \ --regionregion -
The Linux variant requires the sudo_for_job_user
host configuration script. The Windows variant requires the bundle's setup/host_config.ps1as the fleet host configuration script.
Important
The Windows variant gives the RDP user local Administrator access
and adds job-user to Administrators. Use this
configuration for debugging only. Shut down all workers in the fleet
after debugging completes.
Submit the job:
# Linux: 60-minute session ./submit.sh # Linux: 120-minute session ./submit.sh 120 # Windows: 60-minute session ./submit.sh farm-XXXqueue-XXX
Once the job is running, find the managed node ID in the job log and connect:
aws ssm start-session --target mi-XXXXXXXXX--regionregion