@cryptotaxi247 / netdata-1 / commits / 2a0cfeafb

docs: Add cloud.d directory contents section to claim README (#21966)

* docs: Add cloud.d directory contents section to claim README This commit adds a comprehensive inventory section describing the contents of the cloud.d directory: - cloud.conf: Cloud configuration with claimed_id - private.pem: RSA private key for ACLK authentication - public.pem: RSA public key for ACLK authentication - claimed_id: File storing the claimed ID UUID The section includes a note clarifying the distinction between claimed_id and Machine GUID, and cross-references the Node Identities documentation for detailed identity explanations. * Apply suggestion from @Ancairon * Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: nedi-audit <nedi-audit@netdata.io> Co-authored-by: Fotis Voutsas <fotis@netdata.cloud> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

nedi-app[bot] committed Mar 24, 2026 at 15:24 UTC 2a0cfeafb2664ffd66c3e300835968da1996425a
1 file changed +25 -1
src/claim/README.md
+25 -1
@@ -207,10 +207,34 @@ To remove a node from your Space and connect it to another, follow these steps:
207
208 4. **Connect to new Space**
209
210 - Go to your new Space, copy the installation command with the new claim token and run it. If you're using a `docker-compose.yml` file, you will have to overwrite it with the new claiming token. The node should now appear online in that Space.
210 + Go to your new Space, copy the installation command with the new claim token and run it. If you're using a `docker-compose.yml` file, you will have to overwrite it with the new claiming token. The node should now appear online in that Space.
211
212 </details>
213
214 +### `cloud.d` Directory Contents
215 +
216 +When an Agent is claimed to Netdata Cloud, the `cloud.d/` directory (located in your Netdata library directory, typically `/var/lib/netdata/cloud.d/`) stores the credentials and identity information for the Agent-Cloud Link (ACLK). The directory typically includes the following core files:
217 +
218 +| File | Description |
219 +|------|-------------|
220 +| `cloud.conf` | Primary Cloud configuration file, including the canonical `claimed_id` and other ACLK settings |
221 +| `private.pem` | RSA private key for ACLK authentication |
222 +| `public.pem` | RSA public key for ACLK authentication |
223 +| `claimed_id` | Legacy file duplicating the `claimed_id` from `cloud.conf`, kept mainly for backwards compatibility and fallback |
224 +
225 +In addition to these, depending on your configuration and features in use, you may also see the following optional files:
226 +
227 +- `token` / `rooms`: Used for split-file auto-claiming workflows.
228 +- `trusted.pem` / `cloud_fullchain.pem`: Optional custom CA bundle files used to validate the TLS connection to Netdata Cloud.
229 +
230 +:::note
231 +
232 +The `claimed_id` is separate from the Machine GUID. It uniquely identifies the connection between the Agent and Cloud, while the Machine GUID identifies the node itself.
233 +
234 +:::
235 +
236 +For detailed explanations of all identity types and their relationships, see [Node Identities](/docs/learn/node-identities.md).
237 +
238 ### Regenerate Claiming Token
239
240 You may need to revoke your previous Claiming Token and generate a new one for security reasons.