AWS SDK for JavaScript Iot Jobs Data Plane Client for Node.js, Browser and React Native
npm install @aws-sdk/client-iot-jobs-data-planeAWS SDK for JavaScript IoTJobsDataPlane Client for Node.js, Browser and React Native.
IoT Jobs is a service that allows you to define a set of jobs — remote operations
that are sent to and executed on one or more devices connected to Amazon Web Services IoT Core. For example,
you can define a job that instructs a set of devices to download and install application or
firmware updates, reboot, rotate certificates, or perform remote troubleshooting
operations.
Find the endpoint address for actions in the IoT jobs data plane by running this
CLI command:
aws iot describe-endpoint --endpoint-type iot:Jobs
The service name used by Amazon Web Services
Signature Version 4 to sign requests is:
iot-jobs-data.
To create a job, you make a job document which is a description of the remote
operations to be performed, and you specify a list of targets that should perform the
operations. The targets can be individual things, thing groups or both.
IoT Jobs sends a message to inform the targets that a job is available. The target
starts the execution of the job by downloading the job document, performing the operations
it specifies, and reporting its progress to Amazon Web Services IoT Core. The Jobs service provides commands
to track the progress of a job on a specific target and for all the targets of the
job
npm install @aws-sdk/client-iot-jobs-data-planeyarn add @aws-sdk/client-iot-jobs-data-planepnpm add @aws-sdk/client-iot-jobs-data-planeThe AWS SDK is modulized by clients and commands.
To send a request, you only need to import the IoTJobsDataPlaneClient and
the commands you need, for example GetPendingJobExecutionsCommand:
``js`
// ES5 example
const { IoTJobsDataPlaneClient, GetPendingJobExecutionsCommand } = require("@aws-sdk/client-iot-jobs-data-plane");
`ts`
// ES6+ example
import { IoTJobsDataPlaneClient, GetPendingJobExecutionsCommand } from "@aws-sdk/client-iot-jobs-data-plane";
To send a request, you:
- Initiate client with configuration (e.g. credentials, region).
- Initiate command with input parameters.
- Call send operation on client with command object as input.destroy()
- If you are using a custom http handler, you may call to close open connections.
`js
// a client can be shared by different commands.
const client = new IoTJobsDataPlaneClient({ region: "REGION" });
const params = { /* input parameters / };
const command = new GetPendingJobExecutionsCommand(params);
`
#### Async/await
We recommend using await
operator to wait for the promise returned by send operation as follows:
`js`
// async/await.
try {
const data = await client.send(command);
// process data.
} catch (error) {
// error handling.
} finally {
// finally.
}
Async-await is clean, concise, intuitive, easy to debug and has better error handling
as compared to using Promise chains or callbacks.
#### Promises
You can also use Promise chaining
to execute send operation.
`js`
client.send(command).then(
(data) => {
// process data.
},
(error) => {
// error handling.
}
);
Promises can also be called using .catch() and .finally() as follows:
`js`
client
.send(command)
.then((data) => {
// process data.
})
.catch((error) => {
// error handling.
})
.finally(() => {
// finally.
});
#### Callbacks
We do not recommend using callbacks because of callback hell,
but they are supported by the send operation.
`js`
// callbacks.
client.send(command, (err, data) => {
// process err and data.
});
#### v2 compatible style
The client can also send requests using v2 compatible style.
However, it results in a bigger bundle size and may be dropped in next major version. More details in the blog post
on modular packages in AWS SDK for JavaScript
`ts
import * as AWS from "@aws-sdk/client-iot-jobs-data-plane";
const client = new AWS.IoTJobsDataPlane({ region: "REGION" });
// async/await.
try {
const data = await client.getPendingJobExecutions(params);
// process data.
} catch (error) {
// error handling.
}
// Promises.
client
.getPendingJobExecutions(params)
.then((data) => {
// process data.
})
.catch((error) => {
// error handling.
});
// callbacks.
client.getPendingJobExecutions(params, (err, data) => {
// process err and data.
});
`
When the service returns an exception, the error will include the exception information,
as well as response metadata (e.g. request id).
`js`
try {
const data = await client.send(command);
// process data.
} catch (error) {
const { requestId, cfId, extendedRequestId } = error.$metadata;
console.log({ requestId, cfId, extendedRequestId });
/**
* The keys within exceptions are also parsed.
* You can access them by specifying exception names:
* if (error.name === 'SomeServiceException') {
* const value = error.specialKeyInException;
* }
*/
}
Please use these community resources for getting help.
We use the GitHub issues for tracking bugs and feature requests, but have limited bandwidth to address them.
- Visit Developer Guide
or API Reference.
- Check out the blog posts tagged with aws-sdk-js
on AWS Developer Blog.
- Ask a question on StackOverflow and tag it with aws-sdk-js.
- Join the AWS JavaScript community on gitter.
- If it turns out that you may have found a bug, please open an issue.
To test your universal JavaScript code in Node.js, browser and react-native environments,
visit our code samples repo.
This client code is generated automatically. Any modifications will be overwritten the next time the @aws-sdk/client-iot-jobs-data-plane` package is updated.
To contribute to client you can check our generate clients scripts.
This SDK is distributed under the
Apache License, Version 2.0,
see LICENSE for more information.
DescribeJobExecution
Command API Reference / Input / Output
GetPendingJobExecutions
Command API Reference / Input / Output
StartCommandExecution
Command API Reference / Input / Output
StartNextPendingJobExecution
Command API Reference / Input / Output
UpdateJobExecution