Skip to content

Overview

The Remote Provisioning Client (RPC-Go) is a Go-based application that runs directly on a managed device and activates Intel® AMT.

RPC-Go supports two primary deployment models:

  1. Cloud deployment (RPS-driven activation) – RPC-Go acts as a proxy between the Remote Provisioning Server (RPS) and Intel® AMT. This flow is commonly used to configure AMT so that the device can establish a Client Initiated Remote Access (CIRA) connection to the Management Presence Server (MPS).

  2. Local deployment – RPC-Go consumes an exported AMT profile (YAML) and applies it directly on the device. This does not require RPS and is well suited for Console-based workflows, flat networks, or environments where cloud connectivity is not desired.

Activation Flows

1. Activation via Remote Provisioning Server (RPS)

In this flow:

  1. RPC-Go connects to RPS over a secure WebSocket connection.
  2. RPS orchestrates the WS-Management (WSMAN) sequence required to configure and activate Intel® AMT.
  3. RPC-Go relays those commands to AMT through the MEI (HECI) driver or Intel® Local Management Service (LMS).
  4. Once activated and configured, AMT establishes a CIRA tunnel to MPS.
Figure 1: RPC Configuration
Figure 1: RPC Configuration

2. Local Activation Using a Profile (config.yaml / profile YAML)

RPC-Go can also perform activation and configuration locally, without relying on RPS at runtime.

Typical flow:

  1. A profile is created in the Console or RPS UI (e.g., ACM/CCM, network settings, CIRA config).
  2. The profile is exported as YAML (encrypted profile).
  3. RPC-Go is run on the managed device with that profile.
  4. RPC-Go applies the profile to AMT through the MEI driver or Intel® LMS.

This model is useful for environments where profiles are pre-generated, RPS is not required, or a local-only provisioning workflow is preferred.

Versioning

RPC-Go is available in two major versions:

  • v2.x (current stable)
  • v3.x (Beta) — introduces a clearer configuration model and standardized CLI behavior.

If you are using RPC-Go v2.x today, nothing changes and all workflows will continue to function as expected.

For details on the updates in v3.x, see the RPC-Go About v3 page. Additional documentation will be rolled out over the next few weeks.