AWS batch documentation change
Summary
Minor text formatting changes including apostrophe corrections and event name reference adjustments. No functional changes to content.
Security assessment
Changes involve typo fixes (e.g., apostrophe standardization) and minor phrasing adjustments. No security vulnerabilities, mitigations, or security feature additions are addressed.
Diff
diff --git a/batch/latest/userguide/job_stuck_in_runnable.md b/batch/latest/userguide/job_stuck_in_runnable.md index 68f5ad80d..462835551 100644 --- a//batch/latest/userguide/job_stuck_in_runnable.md +++ b//batch/latest/userguide/job_stuck_in_runnable.md @@ -9 +9 @@ Suppose that your compute environment contains compute resources, but your jobs -If AWS Batch detects that you have a `RUNNABLE` job at the head and blocking the queue, you'll receive a [Resource: Job queue blocked events](./batch-job-queue-blocked-events.html) event from Amazon CloudWatch Events with the reason. The same reason is also updated into the `statusReason` field as a part of `[ListJobs](https://docs.aws.amazon.com/batch/latest/APIReference/API_ListJobs.html)` and `[DescribeJobs](https://docs.aws.amazon.com/batch/latest/APIReference/API_DescribeJobs.html)` API calls. +If AWS Batch detects that you have a `RUNNABLE` job at the head and blocking the queue, you'll receive a [Job queue blocked events](./batch-job-queue-blocked-events.html) event from Amazon CloudWatch Events with the reason. The same reason is also updated into the `statusReason` field as a part of `[ListJobs](https://docs.aws.amazon.com/batch/latest/APIReference/API_ListJobs.html)` and `[DescribeJobs](https://docs.aws.amazon.com/batch/latest/APIReference/API_DescribeJobs.html)` API calls. @@ -25 +25 @@ The following are the reasons that AWS Batch provides when it detects that a job - 1. **Reason:** All connected compute environments have insufficient capacity errors. When requested, AWS Batch detects Amazon EC2 instances that experience insufficient capacity errors. Manually canceling the job will allow the subsequent job to move to the head of the queue but without resolving the service role issue(s), it is likely that the next job will also be blocked as well. It’s best to manually investigate and resolve this issue. + 1. **Reason:** All connected compute environments have insufficient capacity errors. When requested, AWS Batch detects Amazon EC2 instances that experience insufficient capacity errors. Manually canceling the job will allow the subsequent job to move to the head of the queue but without resolving the service role issue(s), it is likely that the next job will also be blocked as well. It's best to manually investigate and resolve this issue. @@ -35 +35 @@ The following are the reasons that AWS Batch provides when it detects that a job - 1. The AWS Batch service role requires `autoscaling:DescribeScalingActivities` permission for this detection to work. If you use the [Using service-linked roles for AWS Batch](./using-service-linked-roles.html) service-linked role (SLR) or the [AWS managed policy: AWSBatchServiceRole policy](./security-iam-awsmanpol.html#security-iam-awsmanpol-AWSBatchServiceRolePolicy) managed policy, then you don’t need to take any action because their permission policies are updated. + 1. The AWS Batch service role requires `autoscaling:DescribeScalingActivities` permission for this detection to work. If you use the [Using service-linked roles for AWS Batch](./using-service-linked-roles.html) service-linked role (SLR) or the [AWS managed policy: AWSBatchServiceRole policy](./security-iam-awsmanpol.html#security-iam-awsmanpol-AWSBatchServiceRolePolicy) managed policy, then you don't need to take any action because their permission policies are updated. @@ -57 +57 @@ The following are the reasons that AWS Batch provides when it detects that a job - 4. **Reason:** All compute environments have service role issues. To resolve this, compare your service role permissions to the [AWS managed policies for AWS Batch](./security-iam-awsmanpol.html) and address any gaps. Note:You can’t configure a programmable action through the `jobStateTimeLimitActions` parameter to resolve this error. + 4. **Reason:** All compute environments have service role issues. To resolve this, compare your service role permissions to the [AWS managed policies for AWS Batch](./security-iam-awsmanpol.html) and address any gaps. Note:You can't configure a programmable action through the `jobStateTimeLimitActions` parameter to resolve this error.