Skip to main content

Registration

Registration is how a deployment learns that a node exists: the node's certificate is attached to an AWS IoT Thing, after which — and only after which — the device can connect. The dashboard splits the work across two pages under Node management in the left sidebar.

Generate nodes​

Titled Generate test nodes. Produces everything a small batch needs in one ZIP: per-node credentials, factory NVS binaries, provisioning QR codes, and a node_certs.csv for the registration step. Enter the batch size — the form shows the per-batch maximum — and download.

This is the right tool for development and pilot batches. For manufacturing runs, use the scripted CLI batch flow instead, which also registers and can emit merged flash images.

Register nodes​

Uploads node_certs.csv from the generated ZIP (or one you produced yourself) to register the batch with the deployment. Registration runs as a job, so you watch it in a list rather than waiting on a single click. Optionally pick a group, enable capabilities, and set tags at upload time.

A quota banner on the Nodes page shows registered nodes against your licensed limit.

Generating credentials is not registering them

The single most common dashboard mistake. Generate nodes produces credentials; Register nodes tells the deployment they exist. A node whose certificate was generated but never registered fails TLS at connect time, which looks exactly like a wrong MQTT host. If a device will not connect, check registration before you debug the firmware.

  • Dashboard batch flow — the full walkthrough: generate, register, flash, and what is inside the ZIP
  • Device credentials — how registration fits the identity story, and the alternatives (claiming, CLI batch)