AWS batch documentation change
Summary
Added new troubleshooting entry for unsupported instance type configurations in compute environments, including specific statusReason message and resolution steps. Renumbered subsequent entries.
Security assessment
The change addresses configuration errors and instance type compatibility issues, but does not indicate a security vulnerability or introduce security-related guidance. Focuses on operational troubleshooting rather than security controls.
Diff
diff --git a/batch/latest/userguide/job_stuck_in_runnable.md b/batch/latest/userguide/job_stuck_in_runnable.md index 462835551..d90bd2ce6 100644 --- a//batch/latest/userguide/job_stuck_in_runnable.md +++ b//batch/latest/userguide/job_stuck_in_runnable.md @@ -65 +65,5 @@ Canceling the job, either manually or by setting the `jobStateTimeLimitActions` - 5. **Reason:** All compute environments are invalid. For more information, see [INVALID compute environment](./invalid_compute_environment.html). Note: You can't configure a programmable action through the `jobStateTimeLimitActions` parameter to resolve this error. + 5. **Reason:** Your compute environment has an unsupported instance type configuration. This can occur when instance types are not available in your selected Availability Zones, or when your launch template or launch configuration contains settings incompatible with the specified instance types. To resolve this, verify that your instance types are supported in your specified AWS Region and Availability Zones, check that your launch template settings are compatible with your instance types, and consider updating to newer generation instance types. For more information about finding supported instance types, see [Finding an Amazon EC2 instance type](https://docs.aws.amazon.com/https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-discovery.html) in the _Amazon EC2 User Guide_. + + * **`statusReason` message while the job is stuck:** `MISCONFIGURATION:EC2_INSTANCE_CONFIGURATION_UNSUPPORTED - Your compute environment associated with this job queue has an unsupported instance type configuration.` + + 6. **Reason:** All compute environments are invalid. For more information, see [INVALID compute environment](./invalid_compute_environment.html). Note: You can't configure a programmable action through the `jobStateTimeLimitActions` parameter to resolve this error. @@ -69 +73 @@ Canceling the job, either manually or by setting the `jobStateTimeLimitActions` - 6. **Reason:** AWS Batch has detected a blocked queue, but is unable to determine the reason. Note: You can't configure a programmable action through the `jobStateTimeLimitActions` parameter to resolve this error. For more information about troubleshooting, see [Why is my AWS Batch job stuck in RUNNABLE on AWS](https://repost.aws/knowledge-center/batch-job-stuck-runnable-status) in _re:Post_. + 7. **Reason:** AWS Batch has detected a blocked queue, but is unable to determine the reason. Note: You can't configure a programmable action through the `jobStateTimeLimitActions` parameter to resolve this error. For more information about troubleshooting, see [Why is my AWS Batch job stuck in RUNNABLE on AWS](https://repost.aws/knowledge-center/batch-job-stuck-runnable-status) in _re:Post_.