How azure/iot-identity-service works
Project type and purpose
• This is a Rust-based, microservices-style “device runtime” for Azure IoT devices. It provides a CLI (aziotctl) plus four long-running daemons (aziotd, aziot-certd, aziot-identityd, aziot-keyd, aziot-tpmd) that together manage certificates, identities, keys, and TPM operations on the device.
File structure
• Top-level crates:
• aziotctl – command-line interface
• aziotd – runtime orchestrator daemon
• cert/{aziot-certd, cert-renewal, cert-common…} – certificate service and libraries
• identity/{aziot-identityd, identity-common…, cloud-client…} – identity service and clients
• key/{aziot-keyd, key-common…, openssl-engine…} – key service and crypto engine
• tpm/{aziot-tpmd, tss-minimal…, tpm-clients} – TPM service and TSS libraries
• http-common, config-common – shared HTTP server/client and config-watcher libraries
• Each daemon has its own config folder (default TOML under unix), an OpenAPI spec (for REST routes), and implements HTTP endpoints for management.
• Common backend crates (http-common, *-common-http, *-client-async) factor out client/server logic and protocol models.
README
• Confirms it serves as the Azure IoT Identity Service runtime