- 新しい順
- 投票が多い順
- コメントが多い順
Please check if service role of the compute environment exists. AWS Batch uses service roles to manage EC2 and ECS resources on your behalf. Is the role had been deleted prior to deleting the compute environment, then AWS Batch is not able to delete the compute resources and the enters INVALID state. In case if the role was deleted, then create service role again with the same name and try deleting the compute environment again.
If you don't have a Spot Fleet role, complete the following steps to create one for your compute environment:
-
Open the IAM console.
-
In the navigation pane, choose Roles.
-
Choose Create role.
-
Choose AWS service. Then, choose EC2 as the service that will use the role that you're creating.
-
In the Select your use case section, choose EC2 Spot Fleet Role. Important: Don't choose the similarly named EC2 - Spot Fleet.
-
Choose Next: Permissions.
-
Choose Next: Tags. Then, choose Next: Review.
-
For Role name, enter AmazonEC2SpotFleetRole.
-
Choose Create role. Note: Use your new Spot Fleet role to create new compute environments. Existing compute environments can't change Spot Fleet roles. To get rid of the obsolete environment, deactivate and then delete that environment.
-
Open the AWS Batch console.
-
In the navigation pane, choose Compute environments.
-
Choose the compute environment that's in the INVALID state. Then, choose Disable.
-
Choose Delete.
Deactivate and delete your compute environment You must deactivate and delete your compute environment because the launch template associated with your compute environment doesn't exist. This means that you can't use the compute environment associated with your launch template. You must delete that compute environment, and then create a new compute environment.
-
Open the AWS Batch console.
-
In the navigation pane, choose Compute environments.
-
Select the compute environment that's in the INVALID state. Then, choose Disable.
-
Choose Delete.
-
Create a new compute environment.
Deactivate and then activate your compute environment
-
Open the AWS Batch console.
-
In the navigation pane, choose Compute environments.
-
Choose the compute environment that's in the INVALID state. Then, choose Disable.
-
Choose the same compute environment from step 3. Then, choose Enable.
Related information
The suggested steps:
- Open the AWS Batch console.
- In the navigation pane, choose Compute environments.
- Select the compute environment that's in the INVALID state. Then, choose Disable.
- Choose Delete.
did not work in my situation. The compute environment is still there.
Cheers
関連するコンテンツ
AWS公式更新しました 2年前- AWS公式更新しました 2年前
Yes, the service role still exists.
I have gone into the Batch web ui to look again and see this STATUS
INVALID - CLIENT_ERROR - User: arn:aws:sts::xxxxxxxxxx:assumed-role/batch_role/aws-batch is not authorized to perform: ecs:ListClusters on resource: * because no identity-based policy allows the ecs:ListClusters action (Service: AmazonECS; Status Code: 400; Error Code: AccessDeniedException; Request ID: zzzzzzzzzzzzzzzzzzzzzzzzz; Proxy: null)
Is the deletion problem due to the service role not having the right permissions ? If so, what permission should I set it to ?
Yes, it needs
ecs:ListClustersaction and some others. Please compare your role's permissions with those described in the documentation here https://docs.aws.amazon.com/batch/latest/userguide/service_IAM_role.html