AWS Task Runners
CertifiedEnterprise EditionTask runners that run Kestra workloads on AWS Batch (ECS Fargate/EC2 or EKS compute environments) or natively on a plain EC2 instance.
Batch requires computeEnvironmentArn (and typically jobQueueArn) plus AWS credentials or an assumed role. Set a bucket when using inputFiles, outputFiles, or working directory sync, and ensure the task defines a containerImage. On ECS, tune executionRoleArn and taskRoleArn as needed. On EKS those roles are ignored and IAM access is granted through serviceAccountName with IRSA. Resources, polling, and resume/cleanup options can be tuned to fit your Batch environment. Ec2 ignores containerImage: it launches a plain instance from amiId and runs task commands natively via AWS Systems Manager Run Command, requiring an iamInstanceProfile granting SSM access and an AMI with the SSM Agent installed.
AWS Task Runners
Task runners that run Kestra workloads on AWS Batch (ECS Fargate/EC2 or EKS compute environments) or natively on a plain EC2 instance.
Batch requires computeEnvironmentArn (and typically jobQueueArn) plus AWS credentials or an assumed role. Set a bucket when using inputFiles, outputFiles, or working directory sync, and ensure the task defines a containerImage. On ECS, tune executionRoleArn and taskRoleArn as needed. On EKS those roles are ignored and IAM access is granted through serviceAccountName with IRSA. Resources, polling, and resume/cleanup options can be tuned to fit your Batch environment. Ec2 ignores containerImage: it launches a plain instance from amiId and runs task commands natively via AWS Systems Manager Run Command, requiring an iamInstanceProfile granting SSM access and an AMI with the SSM Agent installed.
