AWS Batch simplifies permissions by introducing Service-Linked Roles
AWS Batch now supports using AWS Identity and Access Management (IAM) service-linked roles, which allows customers to easily delegate permissions to AWS Batch to run their batch computing workloads.
AWS Batch now supports using AWS Identity and Access Management (IAM) service-linked roles, which allows customers to easily delegate permissions to AWS Batch to run their batch computing workloads.
AWS Batch enables developers, scientists, and engineers to easily and efficiently run hundreds of thousands of batch computing jobs on AWS. AWS Batch dynamically provisions the optimal quantity and type of compute resources (e.g., CPU, GPU, or memory-optimized instances) based on the volume and specific resource requirements of the batch jobs submitted. With AWS Batch, there is no need to install and manage batch computing software or server clusters that run your jobs, allowing you to focus on analyzing results and solving problems. AWS Batch plans, schedules, and executes your batch computing workloads across AWS compute services and features, such as Amazon EC2 and EC2 Spot Instances.
The AWS Batch service-linked role is predefined by AWS Batch and includes the permissions that AWS Batch requires to run your batch jobs. Examples include launching Amazon EC2 instances in your account, or joining those instances to an AWS Batch compute environment. A service-linked role makes setting up AWS Batch easier because you don’t have to manually add the necessary permissions.
You don't need to manually create a service-linked role. When you create a Compute Environment in the AWS Batch Console, the AWS CLI, or the AWS API, AWS Batch creates the service-linked role for you. To learn more about AWS Batch and its service-linked role, please visit the AWS Batch documentation.