.png?sv=2022-11-02&spr=https&st=2024-11-23T10%3A05%3A06Z&se=2024-11-23T10%3A15%3A06Z&sr=c&sp=r&sig=D8vED7%2FICs5q1TMyoAF%2BT9dhURLzKplfkj9CMjaHGWA%3D){kind=logo}
Nodes
- 28 Sep 2023
- 1 Minute to read
- Contributors
- Print
- DarkLight
Nodes
- Updated on 28 Sep 2023
- 1 Minute to read
- Contributors
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Nodes provide segmentation of event data, access permissions, deployment configuration, and decisions to particular environments (e.g. prod, staging) or brands.
In a typical configuration, Darwinium provides a staging and a production node, however additional nodes may be added free of charge to suit your needs.
The active node can be switched at any time in Darwinium’s web portal by clicking on the menu at the top right of the screen:
Each node has its own subdomain – this is a randomly generated name assigned when the node is first created. The subdomain is used for API requests (such as enrichment queries) relevant to the node.
Why does Darwinium use subdomains? Why can't this include my company name for convenience?
Darwinium uses subdomains as a means of logically separating traffic in a manner that potentially makes nodes self-sufficient for data residency and compliance. We avoid using customer names for security purposes, as exposing a company name potentially enables targeted attacks and enumeration of DNS records. Some customers in the past have also required on-prem installation of the node, although this has largely been superceded by Edge functionality.
Was this article helpful?