job role. The
Job role configuration field in the UI has this bulrb: "You can optionally specify an IAM role that provides the container in your job with permissions to use the AWS APIs. This feature uses Amazon ECS IAM roles for tasks functionality." That is what you want to use if you want to grant the process in your container access to, say, S3 (or any other AWS service).
job execution role is assigned to the low level agent and it enables it to pull the container image from ECR, it enables it to read from Secrets Manager and pass the secrets to the containers as variable, and a few other low level infra things.
ARM64 support for Batch jobs on AWS FargateAccepted Answerasked 9 months ago
How to set up IAM roles/policies to run Fargate tasks inside a step function?asked 8 months ago
AWS Batch on Fargate: AccessDenied trying to access secrets managerasked a year ago
how to save a file while running an etl job in a fargate task?asked 4 months ago
Which role do I have to use for the Fargate tasks on AWS Batch?Accepted Answerasked a year ago
ECS Fargate tasks not running. Stopping with error CannotPullContainerErrorasked 9 months ago
Why is my EFS File system policy blocking Fargate from mounting the EFS even though it includes the Task Execution Role arn?asked a month ago
S3 Block Public Access + Bucket Policy - Access Deniedasked 8 months ago
AWS FIS able to restrict fargate targets to separate regular ECS from Fargate Batch Jobs?Accepted Answerasked 3 months ago
AWS Fargate Increase Concurrent Running tasksasked 7 months ago