Submit a batch job to the default "WolframBatch" provider:

Check the job's status:

Eventually the status will indicate that the job has finished running:

Retrieve the result of the job and display the first result:

Submit a batch job including a local input file, uploaded under the name "photo.jpg":

Submit a batch job to the "AWSBatch" batch computation provider:

Retrieve the result of the job:

Submit a batch job using the default remote submission environment:

Using the default on-demand licensing settings, RemoteBatchSubmit will refuse to submit a job if your Service Credits balance is insufficient to create a license entitlement based on the job processor count and TimeConstraint :

Reduce the number of processor cores and/or the TimeConstraint :

Alternatively, you may override the balance check by supplying the "CheckCreditsBalance"False entitlement setting to the LicensingSettings option:

RemoteBatchSubmit includes all definitions for all symbols in the code you submit. In some cases this can lead to large job uploads, even when it is not desired:

You can add the IncludeDefinitions option if you do not want any local symbol definitions to be included: