AWS IoT RoboRunner concepts - AWS IoT RoboRunner

AWS IoT RoboRunner concepts

This section describes key concepts and terminology you need to understand to use AWS IoT RoboRunner effectively.


A site defines a physical place such as a facility, building, or a specific area within a building where your workers and worker fleets are located and managed.

A site is used to group your workers in AWS IoT RoboRunner. Creating a site generates a unique Amazon resource name (ARN) that you use with AWS IoT RoboRunner APIs to associate a set of related workers with their physical locations. You can find examples for using the AWS IoT RoboRunner APIs and your site ARNs to integrate AWS IoT RoboRunner with your fleet management systems (FMS).

For more information, see Create a site.


A worker is a robot, vehicle, or any other system that completes tasks for you, including but not limited to automatic guided vehicles (AGV) and autonomous mobile robots (AMR).

Worker fleet

A worker fleet is a group of workers. It is commonly used to group robots from a given manufacturer, a particular type or model of robot, or robots allocated to a particular area or task. You usually start by requesting that a fleet of workers perform a task. Once you are ready to run the task, a single worker meeting the task conditions (such as worker is available) is chosen to perform the task.


A destination is a semantic label attached to coordinates. Examples of destinations include kitchen and living room. Other examples might include maintenance area, docking area, waiting zone, and package unloading area.

Destinations are used to express tasks. For example, a task might be MOVE from destination kitchen to destination living room.


A task is something to be performed. Tasks have dependencies: a task has children tasks which are refined versions of the parent task. A task is mutable, therefore it can be modified by the user.

Node task

A node task is a task with no children. A node task has one or more action templates associated with it. Action templates are actions that are not yet fully defined. For instance, compared to their corresponding action, they are not assigned to a worker.


An activity is a chunk of work ready to be dispatched to a worker. Activities are immutable. This is necessary because internet connectivity between AWS IoT RoboRunner and workers may be interrupted. If activities were mutable, the worker fleet and AWS IoT RoboRunner could become out of sync. There is generally a 1:1 mapping between a task and an activity.


An action is attached to an activity. Actions are primitive data types such as move and wait. You can see actions attached to an activity as a finite-state machine that AWS IoT RoboRunner communicates over the network to define what a worker needs to do. By attaching multiple actions to an activity, you can define complex behaviors such as go to waiting zone, wait until docking area is available, go to docking area, wait until battery charge level is 80% or more, or go back to waiting zone.