You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the awesome work you've done, I tried to put together a very similar stack, without the lambda function.
My jobs were stuck in a Runnable state. After going through this article: https://aws.amazon.com/premiumsupport/knowledge-center/batch-job-stuck-runnable-status/ I saw that the recommended policy for the instance role is AmazonEC2ContainerServiceforEC2Role. (See under "Verify the container instance IAM role")
Based on the awesome work you've done, I tried to put together a very similar stack, without the lambda function.
My jobs were stuck in a
Runnable
state. After going through this article: https://aws.amazon.com/premiumsupport/knowledge-center/batch-job-stuck-runnable-status/ I saw that the recommended policy for the instance role isAmazonEC2ContainerServiceforEC2Role
. (See under "Verify the container instance IAM role")After updating
AmazonECSTaskExecutionRolePolicy
toAmazonEC2ContainerServiceforEC2Role
here:https://github.com/dejonghe/aws-batch-example/blob/master/cloudformation/batch/batch-example.yml#L129 my jobs started going through just fine.
The text was updated successfully, but these errors were encountered: