AWS IoT Device Management Jobs now supports scheduling configuration
Today, we are pleased to announce AWS IoT Device Management Jobs has added a new configuration option for scheduling, which gives customers the flexibility to deploy remote operations during pre-defined time windows so regular usage of their IoT devices is not disrupted. Using the scheduling feature, customers can define the start and end time of a job rollout, and also configure the end behavior to specify what happens to job executions at the end of the job schedule. This new scheduling feature helps customers to set up a rollout schedule in accordance with their standard operating procedures, or a deployment cadence for different types of updates based on their device software development CI/CD cycles.
Today, we are pleased to announce AWS IoT Device Management Jobs has added a new configuration option for scheduling, which gives customers the flexibility to deploy remote operations during pre-defined time windows so regular usage of their IoT devices is not disrupted. Using the scheduling feature, customers can define the start and end time of a job rollout, and also configure the end behavior to specify what happens to job executions at the end of the job schedule. This new scheduling feature helps customers to set up a rollout schedule in accordance with their standard operating procedures, or a deployment cadence for different types of updates based on their device software development CI/CD cycles.
Job scheduling configuration does not require additional device side code and customers who are running Jobs today can immediately take advantage of this capability. Customers can configure Job scheduling through CLI, AWS console, and custom job templates.
AWS IoT Device Management Jobs scheduling configuration can be used in all AWS Regions where AWS IoT Device Management is available. Learn more about the scheduling feature here. To get started with Device Management Jobs for remote operations, refer to its documentation.