--- title: Create a Node --- import OsFamilyGrid from '@site/src/components/OsFamilyGrid'; # Create a Node Use this guide to launch a node from the E2E MyAccount portal. A node is a self-managed compute instance that runs the operating system, plan, storage, networking, security, and backup configuration you choose during creation. You need an E2E MyAccount before you begin. If you do not have one, sign in or create an account from the [E2E MyAccount portal](https://myaccount.e2enetworks.com/). You can also create and manage nodes through the MyAccount API. See [API & Automation](#api--automation) for the API entry point. --- ## Before You Begin Before creating a node, make sure you can sign in to MyAccount and that your account has enough billing access or infra credits to launch the selected plan. You do not need to prepare every networking, storage, or security option in advance. The create-node flow lets you use existing resources or create some of them while launching the node. If you are creating a production node, decide whether you need a VPC, primary public IP, SSH key, backup, or extra volume before you launch. :::warning Caution Nodes are billable resources. Review the Summary and Estimated Cost before you launch. ::: --- ## How to Launch Nodes from MyAccount Portal 1. Log in to [MyAccount](https://myaccount.e2enetworks.com/). 2. In the left navigation, go to Compute > Nodes. 3. Open the node creation flow from the empty-state action or from the node listing page. 4. The portal opens the create-node flow at `/products/create-node`. The current flow has two main stages: | Stage | What you do | | -------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | Select OS | Choose CPU, GPU, or Marketplace, then select the OS, GPU card, or marketplace product. | | Configure and launch | Choose version, category, instance type, plan, billing option, backup, network, security, SSH, volume, and advanced settings. | This page focuses on CPU nodes. GPU and Marketplace options use the same create-node shell, but their available plans and fields can differ. --- ## Step 1: Select OS On the first screen, choose the CPU tab. Use the search field to filter the OS list, then select the OS tile you want. The available OS names and versions are loaded from the portal, so use the portal as the final source for currently available images. Common OS families include: {/* - Ubuntu - Rocky Linux - AlmaLinux - CentOS - Debian - OpenSUSE - Red Hat - Windows - SQL Server images, where available */} :::note You choose the exact OS version on the next screen. The operating system and version should be treated as part of the node's base image selection. ::: --- ## Step 2: Confirm OS Version After you select an OS, the portal opens the plan selection screen. At the top of the screen, review the selected OS and choose the required version from the dropdown. Use the edit icon near the selected OS if you need to choose a different OS family. :::warning Do not launch until the OS and version match your workload. Reinstalling or replacing the OS later can affect application data and access. ::: --- ## Step 3: Select Category and Instance Type Choose the node category and instance family that matches your workload. | Option | When to use it | | ----------------------------- | ------------------------------------------------------------------------------------------------------- | | Linux node | General Linux workloads, application servers, development environments, and standard compute use cases. | | Windows node | Windows workloads that need RDP access and Windows licensing included in the selected plan. | | Linux Smart Dedicated Compute | Workloads that need dedicated compute resources and predictable performance. | For a detailed comparison before you choose, see [Choose a node family](/docs/myaccount/node/getting-started/choose-node-family). The portal then shows instance families such as: | Family | Best fit | | --------- | ------------------------------------------------------------------------------------ | | E1 / E1WC | Cost-sensitive development, testing, and lighter workloads. | | C3 | CPU-intensive workloads such as web servers, batch processing, and analytics. | | M3 | Memory-intensive workloads such as databases, caches, and large in-memory processes. | | SDC3 | Dedicated compute requirements. | | SQL | SQL Server workloads, where SQL images are available. | :::note For E1-series nodes, root storage is configured separately and the node does not include a default public IP. Use VPC, a primary public IP, or post-creation networking based on your access needs. ::: --- ## Step 4: Select a Plan Use the plan dropdown to choose CPU, RAM, storage, and IOPS. The portal shows plan details in a format similar to: ```text - - - ``` For GPU plans, the format can also include GPU memory and CUDA version. For SQL images, the plan can include SQL version information. If the selected family is an E1-series node, configure root storage after selecting the plan. Root storage is charged separately based on the storage size shown in the portal. :::note The plan storage is the node's root disk. Use Volume if you need additional attachable block storage. ::: --- ## Step 5: Review Billing and Estimated Cost The portal shows available billing choices for the selected plan: - On-demand billing, shown as hourly billing with a monthly estimate. - Committed billing, shown as committed plans when available for the selected SKU. Committed plans require an explicit confirmation before launch. The confirmation explains the committed period, the amount that will be charged or deducted, the non-refundable nature of the commitment, and what should happen after the committed period ends. For committed nodes, choose one renewal preference: - Auto-renew the same committed plan. - Switch to hourly billing after the committed period ends. :::warning Caution Do not rely on static documentation for prices or savings percentages. Use the live portal Summary, API response, or approved pricing page for the current amount. ::: :::note Some plans may show a minimum monthly billing notice. Read that notice before launching because the charge can apply immediately on creation and again on the first day of the calendar month. ::: --- ## Step 6: Configure Node Name and Count Use the Summary panel to review and edit: | Field | Requirement | | ------------ | ----------------------------------------------------- | | Node name | Required. Use letters, digits, hyphen, or underscore. | | No. of nodes | Choose 1 to 5 identical nodes. | When you launch multiple nodes: - A specific public IPv4 address cannot be attached during creation. - A volume cannot be attached during creation. - The same configuration is applied to each requested node. :::note If one of several requested nodes fails to start provisioning, the portal reports how many nodes were requested and how many were created. ::: --- ## Step 7: Configure Backup Use the Backup section to decide whether the node should be launched with CDP Backup enabled. In the create-node flow: - Enable backup for production workloads that need recovery points. - Leave backup disabled if you want to configure it later from node settings. - Review any backup warning shown by the portal before launch. Backup encryption is optional during node creation. If you enable it, enter and store the passphrase carefully. :::note For backup retention, restore behavior, encryption details, and troubleshooting, see [CDP Backups](/docs/myaccount/cdp_backups/). ::: If backup cannot be enabled during creation, the node can still be launched without backup. Enable backup later only after fixing the warning or confirming that backup is available for the node. --- ## Step 8: Configure VPC and Public IP Use VPC when the node needs private network communication or better isolation. 1. Turn on the VPC option. 2. Choose an existing VPC. 3. Optionally choose a subnet, if subnets are available for that VPC. 4. For supported public-node configurations, choose whether to assign a default static public IPv4 address. You can create a new VPC or subnet from the create-node flow if your account permissions allow it. :::tip Best Practice If you launch without a VPC, the node can be exposed through public networking depending on the selected plan and IP settings. Use security groups to restrict access. ::: :::note The selected VPC must be in a running state and in the same location as the node. ::: --- ## Step 9: Configure Public IPv4 Use this section when the node must launch with a specific primary public IPv4 address. 1. Turn on the public IPv4 option if shown. 2. Choose an available static public IP. 3. If needed, create a new static public IP from the same section. Specific public IPv4 addresses cannot be attached during creation when you are launching more than one node. In that case, the portal disables the IP selection and you can attach primary public IPs to each node after creation where supported. :::note If you do not select a specific public IPv4 address, the portal may assign a default public IP depending on the selected plan, VPC settings, and availability. E1-series nodes can behave differently, so review the Summary before launch. ::: --- ## Step 10: Review Security Group A security group controls inbound and outbound traffic to the node. MyAccount selects a security group for you by default, so you normally do not need to choose one manually before launch. Your account has a default security group. The default security group is selected automatically in the create-node flow. If no default group is returned, the portal selects the first available security group. The default security group is designed to allow broad inbound and outbound traffic. Before launching a production node, review the selected group and choose or create a stricter group if your workload should only allow specific ports or source IP ranges. Use the create-new control in this section if you need a new rule set. Common access ports: | Access type | Port | | ---------------- | -------- | | SSH for Linux | TCP 22 | | RDP for Windows | TCP 3389 | | CDP Backup agent | TCP 1167 | :::tip Best Practice Avoid allow-all rules, especially rules that open all ports to `0.0.0.0/0`. Restrict access to the ports and source IP ranges your workload requires. ::: --- ## Step 11: Add SSH Keys For Linux nodes, SSH keys are optional but recommended. 1. Select one or more existing SSH keys if you want key-based login. 2. Use the add-new control to register a new SSH key if needed. 3. Disable password-based SSH login only if you want key-only SSH access. :::tip Best Practice Only disable password-based SSH login after selecting at least one valid SSH key and storing the private key safely. ::: If you lose an SSH key later, you can add another SSH key to the node from MyAccount and continue using key-based access. If you also disabled password login, keep at least one working private key available until the replacement key is added. :::note SSH key selection is not shown for Windows nodes. Use RDP credentials for Windows access. ::: --- ## Step 12: Attach a Volume Use Volume to attach an additional block storage volume at launch. 1. Choose a volume in the available state. 2. Use the refresh icon if a newly created volume is not listed yet. 3. Use the create-new control if you need a new volume. Volumes cannot be attached during creation when you are launching more than one node. In that case, the portal disables volume selection and you can attach volumes after the nodes are created. :::note Only available volumes can be attached. If a volume is still creating, wait for it to become available or attach it later. ::: --- ## Step 13: Configure Advanced Settings Expand advanced settings only if your workload needs these options. | Option | What it does | Important note | | ------------ | ------------------------------------------------------------------- | -------------------------------------------------------------------- | | BitNinja | Adds BitNinja server protection where supported. | Not compatible with VPC-only private networking without a public IP. | | Encryption | Enables encryption at rest for the node. | Once enabled, it cannot be disabled for that node. | | IPv6 | Assigns IPv6 when the option is available in the selected location. | Only use it if your application and firewall rules support IPv6. | | Start script | Runs selected scripts when the node starts or reboots. | Keep scripts idempotent so repeated runs do not break the node. | Encryption passphrase rules are validated before launch. If you enter a passphrase, it must be 8 to 12 characters and include lowercase, uppercase, and a special character. --- ## Step 14: Launch the Node Before launching, review the Summary panel: - Node name - Number of nodes - OS and version - Instance type - Configuration - Root storage, if shown - Backup status - VPC - Public IPv4 - Security group - Password-based SSH status - Volume - Estimated cost Click Launch to start provisioning. After launch: - The portal redirects to Compute > Nodes. - The node starts in a provisioning state such as Creating. - The node reaches Running after provisioning completes. - A secure password link is sent to the registered email address. :::note The password link expires after 168 hours. Save the password securely when you retrieve it. ::: --- ## If Something Needs Attention Most setup issues are handled inside the create-node flow before you launch. Some warnings disable only the affected option, while some account or inventory issues can stop the launch request. | Situation | What it means | What to do | | -------------------------------------------------------- | --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | | Backup cannot be enabled for the selected security group | TCP port 1167 is not open for CDP Backup agent communication. | Edit the security group, choose another group, or launch without backup and enable backup later. | | Backup is temporarily unavailable in the selected region | The node can still be launched, but backup will not be enabled during creation. | Launch without backup only if acceptable, then enable backup later. | | Public IP selection is disabled | You are launching multiple nodes, or the selected IP is not available for attachment. | Launch one node if it needs a specific IP, or attach primary public IPs after creation. | | Volume selection is disabled | You are launching multiple nodes, or the volume is not available yet. | Attach the volume after creation, or wait until the volume becomes available. | | VPC or subnet cannot be selected | The network is still creating, unavailable, full, or not valid for the selected node context. | Choose another available VPC/subnet or wait for the network to become ready. | | Request appears instead of launch | The selected plan is temporarily unavailable. | Submit the request from the portal or choose another available plan. | | API returns a billing or credit error | The account does not have enough credit or billing approval for the selected launch. | Add credits or resolve billing verification, then retry. | | API returns a resource limit error | The account has reached a resource limit. | Request additional capacity or reduce the requested configuration. | --- ## API & Automation The public API reference for node creation is available in the MyAccount API docs: - Endpoint: `POST /nodes/` - API docs: [Create a new Node](https://docs.e2enetworks.com/api/myaccount/#/paths/~1nodes~1/post) The portal-backed create request includes fields such as: - `name` - `plan` - `image` - `number_of_instances` - `security_group_id` - `ssh_keys` - `disable_password` - `backups` - `vpc_id` - `subnet_id` - `reserve_ip` - `image_id` for volume attachment - `isEncryptionEnabled` - `start_scripts` - `cn_id` and `cn_status` for committed nodes --- ## Related Resources | Category | Resource | Use it for | | --------------- | ------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------- | | Node management | [Manage Nodes](/docs/myaccount/node/manage) | Start, stop, reboot, rename, delete, and manage existing nodes. | | Access | [Connect to a Linux node](/docs/myaccount/node/connect-to-node/linux-node) | Connect to Linux nodes with SSH. | | Access | [Connect to a Windows node](/docs/myaccount/node/connect-to-node/windows-node) | Connect to Windows nodes with RDP. | | Access | [Connect and use a SQL Server node](/docs/myaccount/node/connect-to-node/sql-node) | Connect to a Windows SQL Server node and configure database access. | | Access | [Launch and use a Marketplace node](/docs/myaccount/node/getting-started/launch-marketplace-node) | Select a marketplace product and access the node after launch. | | Access | [Create a node on a private cluster](/docs/myaccount/node/getting-started/create-private-cluster-node) | Launch a node on dedicated physical hosts assigned to your account. | | Images | [Create Images](/docs/myaccount/node/features/images) | Save a node image and create future nodes from it. | | Snapshots | [Node Snapshots](/docs/myaccount/node/features/snapshots) | Create and manage node snapshots. | | Networking | [VPC](/docs/myaccount/network/vpc) | Use private networking with nodes. | | Networking | [Static Public IPs](/docs/myaccount/network/reserve_ip) | Manage static public IP addresses. | | Networking | [Security Groups](/docs/myaccount/network/security_grp) | Control inbound and outbound traffic. | | Storage | [Block Storage](/docs/myaccount/storage/block_storage) | Create and attach additional volumes. | | Backup | [CDP Backups](/docs/myaccount/cdp_backups/) | Back up and restore nodes. | | Plan selection | [Choose a node family](/docs/myaccount/node/getting-started/choose-node-family) | Compare E1, C3, M3, SDC, SQL, GPU, Marketplace, and private-cluster options. | | Security | [SSH Key Management](/docs/myaccount/security/ssh_key_management) | Create and manage SSH keys. | | Security | [BitNinja](/docs/myaccount/security/bitninja/) | Protect nodes with BitNinja where supported. | | Security | [Node Encryption](/docs/myaccount/node/features/encryption) | Create encrypted nodes. | | Billing | [Committed Nodes](/docs/myaccount/node/troubleshoot/committed-nodes) | Understand committed-node behavior and renewal options. | ## Next Step After the node reaches Running, connect to it: - For Linux, follow [Connect to a Linux node](/docs/myaccount/node/connect-to-node/linux-node). - For Windows, follow [Connect to a Windows node](/docs/myaccount/node/connect-to-node/windows-node). - For SQL Server images, follow [Connect and use a SQL Server node](/docs/myaccount/node/connect-to-node/sql-node) after RDP access works. ---