Nodes

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.

Create New Node

Creating a new node is performed by Darwinium staff upon initial setup and on demand when required.

Contact your Darwinium support representative with:

Node name: name that will appear in node switching drop-down.
Examples: development > test > staging > production
S3 Type:
- Custom (strongly recommended): if hosting encypted PII in an S3 bucket you will own.
  When custom S3, the S3 bucket details should be added soon after to the node config, before any events are generated.
  See: https://docs.darwinium.com/docs/byo-s3-event-storage
- Default if OK with Darwinium hosting the events S3 bucket with encrypted PII

After creating, be sure to update Roles to allow the new node to be accessed by Portal users.
See: https://docs.darwinium.com/docs/configuring-roles-access

Documentation Index

Nodes

Create New Node