Submitting a job - AWS Batch

Submitting a job

After you registered a job definition, you can submit it as a job to an AWS Batch job queue. Many of the parameters that are specified in the job definition can be overridden at runtime.

To submit a job

  1. Open the AWS Batch console at https://console.aws.amazon.com/batch/.

  2. From the navigation bar, select the AWS Region to use.

  3. In the navigation pane, choose Jobs, Submit job.

  4. For Job name, choose a name for your job. The name must be unique.

  5. For Job definition, choose a previously created job definition for your job. For more information, see Creating a single-node job definition .

  6. For Job queue, choose a previously created job queue. For more information, see Creating a job queue.

  7. For Job type, choose Single for a single job or Array to submit an array job. For more information, see Array jobs. This option isn't available for multi-node parallel jobs.

  8. (Array jobs only) For Array size, specify an array size between 2 and 10,000.

  9. (Optional) Declare any job dependencies. A job may have up to 20 dependencies. For more information, see Job dependencies.

    1. For Job depends on, enter the job IDs for any jobs that must finish before this job starts.

    2. (Array jobs only) For N-To-N job dependencies, specify one or more job IDs for any array jobs. The child job index of the jobs that you specify depend on the dependency. For example, JobB:1 depends on JobA:1.

    3. (Array jobs only) Select Run children sequentially to create a SEQUENTIAL dependency for the current array job. This ensures that each child index job waits for its earlier sibling to finish. For example, JobA:1 depends on JobA:0.

  10. For Job attempts, specify the maximum number of times to attempt your job if it fails. For more information, see Automated job retries.

  11. (Optional) For Execution timeout, specify the maximum number of seconds for your job to attempt to run before timing out. If an attempt exceeds the timeout duration, it's stopped and the status moves to FAILED. For more information, see Job timeouts.

    Important

    Jobs that run on Fargate resources can't expect to run for more than 14 days. After 14 days, the Fargate resources might no longer be available and the job is terminated.

  12. (Optional) In the Parameters section, you can specify parameter substitution default values and placeholders to use in the command that your job's container runs when it starts. For more information, see Parameters.

    1. Choose Add parameter.

    2. For Key, specify the key for your parameter.

    3. For Value, specify the value for your parameter.

  13. For vCPUs, specify 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.

  14. For Memory, specify the hard limit (in MiB) of memory to present to the job's 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.

  15. (Optional) For Number of GPUs, specify the number of GPUs your job uses.

    The job runs on a container with the specified number of GPUs pinned to that container.

  16. For Command, specify the command to pass to the container. For simple commands, you can enter the command the same way you do on a command prompt in the Space delimited tab. Verify that the JSON result, which is passed to the Docker daemon, is correct. For more complicated commands (for example, with special characters), you can switch to the JSON tab and enter the string array equivalent there.

    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, go to https://docs.docker.com/engine/reference/builder/#cmd.

    Note

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

  17. (Optional) You can specify environment variables to pass to your job's container. This parameter maps to Env in the Create a container section of the Docker Remote API and the --env option to docker run.

    Important

    We don't recommend using plaintext environment variables for sensitive information, such as your credentials.

    1. Choose Add environment variable.

    2. For Key, specify the key for your environment variable.

      Note

      Environment variables must not start with AWS_BATCH; this naming convention is reserved for variables that are set by the AWS Batch service.

    3. For Value, specify the value for your environment variable.

  18. (Optional) In the Tags section, you can specify the key and value for each tag to associate with the job. For more information, see Tagging your AWS Batch resources.

  19. Choose Submit job.

    Note

    Logs for RUNNING, SUCCEEDED, and FAILED jobs are available in CloudWatch Logs. The log group is /aws/batch/job, and the log stream name format is as follows: first200CharsOfJobDefinitionName/default/ecs_task_id. This format might change in the future.

    After a job reaches the RUNNING status, you can programmatically retrieve its log stream name with the DescribeJobs API operation. For more information, see View Log Data Sent to CloudWatch Logs in the Amazon CloudWatch Logs User Guide. By default, these logs never expire. However, you can modify the retention period. For more information, see Change Log Data Retention in CloudWatch Logs in the Amazon CloudWatch Logs User Guide.