AWS deadline-cloud documentation change
Summary
Removed PDF link, job processing workflow details, browser warning message, and user feedback sections from documentation
Security assessment
Changes involve content removal of general workflow explanations and UI elements. No security vulnerabilities or security feature updates are mentioned in the removed content. The 120-day job retention policy removal lacks explicit security context.
Diff
diff --git a/deadline-cloud/latest/userguide/jobs-running.md b/deadline-cloud/latest/userguide/jobs-running.md index 4fef5d200..8b1378917 100644 --- a//deadline-cloud/latest/userguide/jobs-running.md +++ b//deadline-cloud/latest/userguide/jobs-running.md @@ -1 +0,0 @@ -[](/pdfs/deadline-cloud/latest/userguide/user-guide.pdf.pdf#jobs-running "Open PDF") @@ -3,39 +1,0 @@ -[Documentation](/index.html)[AWS Deadline Cloud](/deadline-cloud/index.html)[User Guide](what-is-deadline-cloud.html) - -# How Deadline Cloud processes jobs - -To process a job, AWS Deadline Cloud uses the Open Job Description (OpenJD) job template to determine the resources needed. Deadline Cloud selects a suitable worker for a step from the fleets associated with your queue. The selected worker meets all of the capability attributes required for the step. - -Next, Deadline Cloud sends instructions to the workers to set up a session for the step. The software required for the step must be available on the worker instance for the job to run. The service can open sessions on multiple workers if the scaling settings for the fleet have capacity. - -You can set up the software in an Amazon Machine Image (AMI), or your worker can load the software at runtime from a repository or package manager. You can use queue, job, or step environments to deploy the software that you prefer. - -The Deadline Cloud service uses the OpenJD template to determine the steps required for the job, and the tasks required for each step. Some steps have dependencies on other steps, so Deadline Cloud determines the order to complete the steps. Then, Deadline Cloud sends the tasks for each step to workers to process. When a task is finished, the service sends another task in the same session, or the worker can start a new session. - -You can track the progress of the job in the Deadline Cloud monitor, the Deadline Cloud command line interface (Deadline Cloud CLI) or the AWS CLI. For more information about using the monitor, see [Using the Deadline Cloud monitor](./working-with-deadline-monitor.html). For more information about using the Deadline Cloud CLI, see [Job states in Deadline Cloud](./jobs-states.html). - -After all tasks in each step are finished, the job is complete and the output is ready to download to your workstation. Even if the job didn't finish, the output from each step and task that finished is available to download. - -Deadline Cloud removes jobs 120 days after they were submitted. When a job is removed, all of the steps and tasks associated with the job are also removed. If you need to re-run the job, submit the OpenJD template for the job again. - - **Javascript is disabled or is unavailable in your browser.** - -To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. - -[Document Conventions](/general/latest/gr/docconventions.html) - -Modify jobs - -Create resource limits for jobs - -Did this page help you? - Yes - -Thanks for letting us know we're doing a good job! - -If you've got a moment, please tell us what we did right so we can do more of it. - -Did this page help you? - No - -Thanks for letting us know this page needs work. We're sorry we let you down. - -If you've got a moment, please tell us how we can make the documentation better.