Creating a single-node job definition on AWS Fargate resources - AWS Batch

Creating a single-node job definition on AWS Fargate resources

To create a new job definition on AWS Fargate resources:

  1. Open the AWS Batch console at AWS Batch console first-run wizard.

  2. From the top navigation bar, choose the Region to use.

  3. In the left navigation pane, choose Job definitions.

  4. For Job definitions, choose Create.

  5. Fror Job type, choose Single-node.

  6. For Name, enter a unique name for your job definition. The name can be up to 128 characters in length. It can contain uppercase and lowercase letters, numbers, hyphens (-), and underscores (_).

  7. For Execution timeout, enter the timeout value (in seconds). The execution timeout is the length of time before an unfinished job is terminated. If an attempt exceeds the timeout duration, it's stopped and the status moves to FAILED. For more information, see Job timeouts. The minimum value is 60 seconds.

  8. (Optional) Turn on Scheduling priority. Enter a scheduling priority value between 0 and 100. Higher values are given higher priority.

  9. (Optional) Expand Additional tags configuration, and then choose Add tag to add tags to the resource.

  10. (Optional) Turn on Propagate tags to propagate tags from the job and job definition.

  11. For Platform type, choose Fargate . For more information, see AWS Batch on AWS Fargate.

  12. (Optional) For Fargate platform version, enter a specific runtime environment version.

  13. (Optional) Turn on Assign public IP to assign a public IP address to a Fargate job network interface. For a job that's running in a private subnet to send outbound traffic to the internet, the private subnet requires a NAT gateway be attached to route requests to the internet. You might want to do this so that you can pull container images. For more information, see Amazon ECS task networking in the Amazon Elastic Container Service Developer Guide.

  14. For Execution role, specify an IAM role that grants the Amazon ECS container and Fargate agents permission to make AWS API calls on your behalf. This feature uses Amazon ECS IAM roles for task functionality. For more information, including configuration prerequisites, see Amazon ECS task execution IAM roles in the Amazon Elastic Container Service Developer Guide.

  15. In the Job Configuration section:

    1. For Image, choose the Docker image to use for your job. Images in the Docker Hub registry are available by default. You can also specify other repositories with repository-url/image:tag. Up to 255 letters (uppercase and lowercase), numbers, hyphens, underscores, colons, periods, forward slashes, and number signs are allowed. This parameter maps to Image in the Create a container section of the Docker Remote API and the IMAGE parameter of docker run

      Note

      Docker image architecture must match the processor architecture of the compute resources that they're scheduled on. For example, ARM-based Docker images can only run on ARM-based compute resources.

      • Images in Amazon ECR Public repositories use the full registry/repository[:tag] or registry/repository[@digest] naming conventions. For example, public.ecr.aws/registry_alias/my-web-app:latest.

      • Images in Amazon ECR repositories use the full registry/repository[:tag] naming convention. For example, aws_account_id.dkr.ecr.region.amazonaws.com/my-web-app:latest.

      • Images in official repositories on Docker Hub use a single name (for example, ubuntu or mongo).

      • Images in other repositories on Docker Hub are qualified with an organization name (for example, amazon/amazon-ecs-agent).

      • Images in other online repositories are qualified further by a domain name (for example, quay.io/assemblyline/ubuntu).

    2. For Command syntax, choose Bash or JSON.

    3. For Command, choose Bash or JSON and then specify the command to pass to the container. For simple commands, you can enter the command as you do for a command prompt and then verify that the JSON result is correct. It's passed to the Docker daemon. For more complicated commands (for example, with special characters), you can use JSON syntax.

      Tip

      Choose Info to view Bash and JSON code samples.

      This parameter maps to Cmd in the Create a container section of the Docker Remote API and the COMMAND parameter to docker run. For more information about the Docker CMD parameter, see https://docs.docker.com/engine/reference/builder/#cmd.

      Note

      You can use default values for parameter substitution and placeholders in your command. For more information, see Parameters.

    4. For vCPUs, enter the number of vCPUs to reserve for the container. This parameter maps to CpuShares in the Create a container section of the Docker Remote API and the --cpu-shares option to docker run. Each vCPU is equivalent to 1,024 CPU shares. You must specify at least one vCPU.

    5. For Memory, enter the memory limit available to the container. If your container attempts to exceed the memory specified here, the container is stopped. This parameter maps to Memory in the Create a container section of the Docker Remote API and the --memory option to docker run. You must specify at least 4 MiB of memory for a job.

      Note

      You can maximize your resource utilization by prioritizing memory for jobs of a specific instance type. For instructions, see Compute Resource Memory Management.

    6. (Optional) Turn on Environment variables configuration to add environment variables as name-value pairs. These variables are passed to the container.

    7. (Optional) Turn on Job Role configuration to add IAM roles that have permissions to the AWS APIs. This feature uses Amazon ECS IAM roles for task functionality. For more information, see IAM Roles for Tasks in the Amazon Elastic Container Service Developer Guide.

      Note

      A job role is required for jobs that runs on Fargate resources.

      Note

      Only roles that have the Amazon Elastic Container Service Task Role trust relationship are shown here. For more information about creating an IAM role for your AWS Batch jobs, see Creating an IAM Role and Policy for your Tasks in the Amazon Elastic Container Service Developer Guide.

    8. (Optional) Turn on Security configuration to add user names for use in the container.

      To give your job's container elevated permissions on the host instance (similar to the root user), drag the Privileged slider to the right. This parameter maps to Privileged in the Create a container section of the Docker Remote API and the --privileged option to docker run.

      For User, enter the user name to use inside the container. This parameter maps to User in the Create a container section of the Docker Remote API and the --user option to docker run.

    9. (Optional) Turn on Secrets to add secrets as a name-value pair. These secrets are exposed in the container. For more information, see secretOptions in Job definition parameters

    10. (Optional) Turn on Enable read only filesystem to remove write access to the volume.

    11. (Optional) Turn on Mount points configuration to add mount points for data volumes. You must specify the source volume and container path. These mount points are passed to the Docker daemon on a container instance.

    12. (Optional) Turn on Volumes configuration to create a list of volumes to pass to the container. Enter Name and Source path for the volume, and then choose Add volume.

    13. (Optional) Turn on Linux parameter configuration to add devices or turn on Linux specific settings such as Init process enabled:

      1. Turn on Init process enabled to run an init process inside the container. This process forwards signals and reaps processes.

    14. (Optional) Turn on Log configuration to add a customer log driver to the container:

      Note

      By default, the awslogs log driver is used.

      1. For Log driver, choose the log driver to use. For more information about the available log drivers, see logDriver in Job definition parameters.

      2. (Optional) For Options, choose Add option to add an option. Enter a name-value pair, and then choose Add option.

      3. (Optional) Turn on Secrets. Enter a name-value pair, and then choose Add to add a secret.

        Tip

        For more information, see secretOptions in Job definition parameters.

  16. (Optional) You can add parameters to the job definition as name-value mappings to override the job definition defaults. To add a parameter:

    1. For Parameters, enter a name-value pair, then choose Add parameter.

      Important

      If you choose Add parameter, you must configure at least one parameter or choose Remove parameter

  17. (Optional) In the Retry Strategies section, you configure the number of times a failed job is resubmitted. You can also configure exit codes and status reasons to help troubleshoot a failed instance. To configure a retry strategy:

    1. For Job attempts, enter the number of times to resubmit a failed job.

    2. (Optional) Choose Add evaluate on exit. Enter at least one parameter value, and then choose an Action. For each set of conditions, Action must be set to either Retry (to retry until the number of job attempts has been reached) or Exit (to stop retrying the job).

      Important

      If you choose Add evaluate on exit, you must configure at least one parameter and choose an Action or choose Remove evaluate on exit.

  18. Choose Create.