Deploy multi-network device meshes using Device Connect server and NATS

Who is this for?

This Learning Path is for developers who have completed the Device-to-device Learning Path and want to build a globally connected fleet of devices and AI agents on top of their Device Connect mesh. You'll add a server layer that gives you persistent registry, distributed state, and security features (commissioning, ACLs) so devices and agents on different networks can find and call each other through a single namespace. If you're new to Device Connect, start with the device-to-device Learning Path first.

What will you learn?

Upon completion of this Learning Path, you will be able to:

• Understand what the Device Connect server adds on top of the edge SDK and when you'd reach for it
• Provision a hosted tenant on the Device Connect portal and download per-device NATS credentials
• Commission an example primary device and a secondary device against your tenant using the credentials the portal issues
• Discover and invoke commissioned devices from a Python client using `device-connect-agent-tools`
• Connect a Strands AI agent to the same tenant

Prerequisites

Before starting, you will need the following:

• Complete the Device-to-device Learning Path to understand Device Connect edge SDK basics
• An account on the Device Connect portal
• A Raspberry Pi 5, another Linux device, or your development machine to use as the example primary device
• A development machine for the secondary device and Python client
• Basic familiarity with Python and the command line