Creating a Node
Environments are simply empty namespaces until they are populated with nodes. To create a node:
- Navigate to your environment home page and click the + ADD dropdown in the top right of the screen.
- Select New Node
- A node requires three pieces of configuration for the initial setup
- Owning member – if you have multiple memberships under your organization’s control, you can use this dropdown to bind the node to a membership of your choice. This is particularly useful for scenarios where a proxy operator is managing the network on behalf of other organizations or where an organization has multiple departments and wants to logically partition resources.
- Name – a string identifying the node in the environment. This does not need to contain the name or membership of the owning organization as this information will be clearly displayed in the environment dashboard
- Deployment Region – the cloud and underlying region where the node will be deployed. If the environment is deployed as single region, then the region is inherited from the environment configuration. If the environment is deployed as a hybrid multi-region, then any whitelisted regions will be available for choice.
- Click Next to continue
The second layer of node configuration is the optional integration with native cloud services. These include KMS for additional encryption of the file system, CloudWatch Log Streams for analytics/troubleshooting, S3 Backups for data persistence and PrivateLink connections for non-public traffic.
Refer to the Using AWS Cloud Integrations ✅article within the DevOps category for more information on configuring integrations.
Size and Role
The last piece of configuration is to choose a size and role for the node. Each size has a direct correlation to ingress rate limiting and underlying memory CPU. Refer to the Rate Limiting and Resource Limitations article to learn more about the specific limitations. The role of “signer” refers to the node’s responsibility in the environment’s consensus algorithm. Any signing node will append its digital signature to the proposed block’s header during IBFT and clique PoA voting rounds.