AWS deadline-cloud: Deadline Cloud SSH-to-worker example: editorial rewrite, tier step removed
Summary
Rewrites the ssh_to_smf job bundle example: rewords the SSM hybrid activation and IAM role setup steps, removes the obsolete `aws ssm update-service-setting` advanced-instances tier command and adds a note that the tier no longer exists, and reorders the host-configuration script guidance.
Security assessment
The diff is an editorial/functional rewrite of an existing example that grants SSH/RDP/PowerShell access to workers via Session Manager. The IAM role line is a rewording of pre-existing guidance (same role name, trust principal, and managed policy), and the removed command is the obsolete advanced-instances tier setting, not a security control. No vulnerability, CVE, or new security guidance is introduced.
Evidence
+ 1. Create an IAM role named `SSMServiceRole`. Add the SSM service principal as the trust and attach the `AmazonSSMManagedInstanceCore` managed policy.
Diff
diff --git a/deadline-cloud/latest/developerguide/examples-jb-ssh-to-worker.md b/deadline-cloud/latest/developerguide/examples-jb-ssh-to-worker.md index 24d4cd2..388d47d 100644 --- a//deadline-cloud/latest/developerguide/examples-jb-ssh-to-worker.md +++ b//deadline-cloud/latest/developerguide/examples-jb-ssh-to-worker.md @@ -9 +9 @@ -The [ssh_to_smf](https://github.com/aws-deadline/deadline-cloud-samples/tree/mainline/job_bundles/ssh_to_smf) (Linux) and [ssh_to_smf_windows](https://github.com/aws-deadline/deadline-cloud-samples/tree/mainline/job_bundles/ssh_to_smf_windows) (Windows) job bundles on the GitHub website register a Deadline Cloud worker as an SSM hybrid managed node, enabling SSH, RDP, or PowerShell access through Session Manager for the duration of the job. Use these bundles to debug a job interactively or to forward ports for web UIs and Jupyter notebooks running on the worker. +The [ssh_to_smf](https://github.com/aws-deadline/deadline-cloud-samples/tree/mainline/job_bundles/ssh_to_smf) (Linux) and [ssh_to_smf_windows](https://github.com/aws-deadline/deadline-cloud-samples/tree/mainline/job_bundles/ssh_to_smf_windows) (Windows) job bundles on the GitHub website give SSH, RDP, or PowerShell access to Deadline Cloud workers. Each bundle registers the worker as an SSM hybrid managed node through Session Manager during the job. Use these bundles to debug a job on the worker. You can also forward ports for web UIs and Jupyter notebooks. @@ -13 +13 @@ The job follows this sequence: - 1. The submit script creates a one-time SSM hybrid activation by calling `aws ssm create-activation`. + 1. The submit script starts a one-time SSM hybrid activation by calling `aws ssm create-activation`. @@ -15 +15 @@ The job follows this sequence: - 2. 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. + 2. The Deadline Cloud job runs on a worker and registers it as a managed node. The job prints the `mi-*` node ID to the job log. @@ -19 +19 @@ The job follows this sequence: - 4. After the configured session duration, the job deregisters the node and cleans up. + 4. After the session time expires, the job removes the node and cleans up. @@ -24 +24 @@ The job follows this sequence: -###### To set up SSH access for one-time per account and Region +###### To set up SSH access (one time per account and Region) @@ -26 +26 @@ The job follows this sequence: - 1. Create an IAM role named `SSMServiceRole` with the SSM service principal trust and the `AmazonSSMManagedInstanceCore` managed policy attached. + 1. Create an IAM role named `SSMServiceRole`. Add the SSM service principal as the trust and attach the `AmazonSSMManagedInstanceCore` managed policy. @@ -28 +28 @@ The job follows this sequence: - 2. Enable the advanced-instances tier: + 2. For the Linux variant, use the [sudo_for_job_user](https://github.com/aws-deadline/deadline-cloud-samples/tree/mainline/host_configuration_scripts/sudo_for_job_user) script on the GitHub website. For the Windows variant, use the bundle's `setup/host_config.ps1` script. @@ -30,4 +29,0 @@ The job follows this sequence: - aws ssm update-service-setting \ - --setting-id "arn:aws:ssm:region:account-id:servicesetting/ssm/managed-instance/activation-tier" \ - --setting-value "advanced" \ - --region region @@ -35 +30,0 @@ The job follows this sequence: - 3. The Linux variant requires the [sudo_for_job_user](https://github.com/aws-deadline/deadline-cloud-samples/tree/mainline/host_configuration_scripts/sudo_for_job_user) host configuration script on the GitHub website, and the Windows variant requires the bundle's `setup/host_config.ps1` as the fleet host configuration script. @@ -37,0 +33 @@ The job follows this sequence: +###### Note @@ -38,0 +35 @@ The job follows this sequence: +The advanced-instances tier no longer exists. You don't need a tier setting to use Session Manager on hybrid managed nodes. @@ -42 +39 @@ The job follows this sequence: -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. +The Windows variant gives the RDP user local Administrator access. It also adds `job-user` to `Administrators`. Use this setup for debugging only. Shut down all workers in the fleet after you finish debugging. @@ -54 +51 @@ Submit the job: - ./submit.sh farm-XXX queue-XXX + ./submit.sh farm-XXXX queue-YYYY @@ -56 +53 @@ Submit the job: -Once the job is running, find the managed node ID in the job log and connect: +After the job starts, find the managed node ID in the job log and connect: