2 Answers
- Newest
- Most votes
- Most comments
0
Are you deploying this in an AWS Organization? Have you checked if the service is enabled or not? This is an error that AWS returns when integrations are disabled at org level. Also check if the role already exists, these roles usually are created automatically by AWS when you use the service.
answered a year ago
Thanks, esgrano. I am not deploying this in an AWS Organization. The AWSBatchServiceRole role does not exist in my account now.
0
Ok, I finally found that the right way of creating it is using CLI......... aws iam create-service-linked-role --aws-service-name batch.amazonaws.com
The arn of the role created this way will be different though: arn:aws:iam:: ************::role/aws-service-role/batch.amazonaws.com/AWSServiceRoleForBatch
answered a year ago
Relevant content
- asked 2 years ago
- Accepted Answerasked 2 months ago
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
I found a workaround......since the name ''AWSBatchServiceRole" is reserved, I change it to a different name "my_AWSBatchServiceRole". Then in the console, I went to AWS Batch/Compute environments, selected the invalid compute environment, clicked on the "Edit" button, and changed its associated role from "AWSBatchServiceRole" to "my_AWSBatchServiceRole". After doing this, I was able to delete it successfully.