AWS batch documentation change
Summary
Added new troubleshooting sections for SageMaker jobs stuck in RUNNABLE status, including automatic remediation documentation
Security assessment
The additions focus on operational troubleshooting (capacity issues and misconfigurations) and introduce automatic remediation features. No security vulnerabilities, access controls, or data protection mechanisms are mentioned. The content addresses runtime job management without security context.
Diff
diff --git a/batch/latest/userguide/troubleshooting.md b/batch/latest/userguide/troubleshooting.md index e7ed049fd..9b906e058 100644 --- a//batch/latest/userguide/troubleshooting.md +++ b//batch/latest/userguide/troubleshooting.md @@ -87,0 +88,10 @@ AWS Batch uses IAM policies, roles, and permissions, and runs on Amazon EC2, Ama + * [AWS Batch for SageMaker Training jobs](./batch-sm-troubleshooting.html) + + * [Jobs stuck in a RUNNABLE status](./sm_job_stuck_in_runnable.html) + + * [Jobs stuck in RUNNABLE due to capacity](./sm_job_stuck_in_runnable_capacity.html) + + * [Jobs stuck in RUNNABLE due to misconfiguration](./sm_job_stuck_in_runnable_misconfiguration.html) + + * [Automatic remediation with jobStateTimeLimitActions](./sm_job_stuck_in_runnable_time_limit_actions.html) +