Launch a Marketplace Node
Use this guide to understand and create a node from a prebuilt marketplace product in MyAccount. The Marketplace tab in the create-node flow lets you pick a product image built by E2E Networks or a vendor instead of a plain OS image. The rest of the creation flow — plan, billing, networking, security, and launch — works the same as any other node.
For the full node creation reference including all fields and options, see Create a node.
What Marketplace Nodes Are
A marketplace node is a normal E2E Node launched from a prebuilt product image. The image already includes an operating system plus a prepared software stack, application, or appliance, so you can start from a ready-made environment instead of installing every package on a clean server.
Marketplace products can cover application stacks and tools such as workflow platforms, web frameworks, databases, control panels, AI applications, or licensed software. For example, a marketplace image might provide an Apache Airflow environment or a Django framework server image on top of a Linux base OS. The exact software, version, ports, credentials, and first-run steps depend on the product you select.
The broader E2E Marketplace includes multiple solution types, including VM images, Kubernetes Helm charts, SaaS integrations, AI applications, and software license add-ons. In MyAccount node creation, the Marketplace tab shows the enabled marketplace products that can be delivered as nodes for your account and location.
Use a marketplace node when:
- You want a faster starting point than a plain OS image.
- The product's included application stack matches your workload.
- You are comfortable managing the launched node, security group, updates, data, and application configuration after provisioning.
Choose a CPU or GPU OS image instead when:
- You need a clean server with no preinstalled application stack.
- You need full control over installation steps and package versions.
- The marketplace product does not match your required OS, version, ports, or licensing model.
A marketplace node is still your compute node after launch. Unless the product documentation says otherwise, you manage OS updates, application updates, access control, backups, and exposed ports the same way you would for any other self-managed node.
Before You Begin
Make sure you can sign in to MyAccount and that your account has enough billing access or infra credits to launch the selected plan.
Nodes are billable resources. Review the Summary and Estimated Cost before you launch.
Step 1: Open the Marketplace Tab
- Log in to MyAccount.
- Go to Compute > Nodes.
- Open the node creation flow.
- On the first screen, select the Marketplace tab.
The portal loads the available marketplace products. Each product card shows the product name, base OS, and version.
Use the search field to filter products by name. To browse the full catalog before selecting, use the Explore all Marketplace Solutions link at the top right of the product list. This opens the E2E Marketplace in a new tab.
Some products are only available to specific accounts and are not visible in all locations. If no products appear, continue with a CPU or GPU node instead.
Step 2: Select a Product
Click a product card to select it. A Selected indicator appears on the card.
After selection, the portal moves to the plan and configuration screen. The breadcrumb at the top updates to reflect the current step. The selected product name, OS, and version appear in a summary at the top of the screen. Use the edit icon next to this summary if you need to go back and choose a different product.
Step 3: Review Product Details
Before selecting a plan, review the product detail section on the plan screen.
| Section | What it contains |
|---|---|
| Overview | Product description and feature list. Use View More to see the full list. |
| Additional Documentation | Release notes for this product version, plus any extra documentation from the vendor. |
| Legal | End User License Agreement for the product. |
Read the legal terms and the additional documentation before you launch. The additional documentation may include the ports the product requires. You will configure the security group in a later step.
Step 4: Select Instance Type and Plan
The marketplace path does not show a version picker. The OS and version are fixed by the product you selected.
Select the instance type and plan the same way you would for a CPU node. If the vendor recommends a specific instance type, it may appear in the additional documentation.
For a comparison of instance types and families, see Choose a node family.
Step 5: Review Billing
Choose On-Demand or a committed plan from the Instance Pricing section. The portal shows the hourly rate and monthly estimate for On-Demand, and the committed price for available committed plans.
Do not rely on static documentation for prices. Use the live portal Summary and Estimated Cost for the current amount.
Step 6: Configure Backup, Network, and Security
Configure the remaining options the same as for any node. The following are the settings most relevant for marketplace nodes.
Backup: Enable CDP Backup if the node needs recovery points. You can enable it later from node settings if you skip it during creation.
VPC and Public IP: Use VPC for private network isolation. If the application must be reachable from the internet, confirm the public IP assignment shown in the Summary.
Security group: Your account always has a default security group that is pre-selected in the creation flow. Before launch, review what ports the product requires from the additional documentation and update the security group to allow only those ports.
Common ports marketplace applications use:
| Access type | Port |
|---|---|
| SSH for Linux | TCP 22 |
| HTTP | TCP 80 |
| HTTPS | TCP 443 |
Actual port requirements vary by product. Check the additional documentation for what the specific product needs.
SSH keys: Optional for Linux-based marketplace nodes. Select one or more keys for key-based login. You can also add keys from the node details page after the node is running.
Volume, advanced settings: Work the same as for any other node. See Create a node for details.
Step 7: Launch the Node
Review the Summary panel before clicking Launch:
- Product name, OS, and version
- Instance type and plan
- Backup status
- VPC and public IP
- Security group
- Estimated cost
Click Launch. The portal redirects to Compute > Nodes. The node starts provisioning and reaches Running after provisioning completes. A secure password link is sent to the registered email address.
The password link expires after 168 hours. Save the password securely when you retrieve it.
Connect to the Node After Launch
Most marketplace products run on a Linux base. Connect to the node with SSH after it reaches Running.
- Go to Compute > Nodes.
- Find the marketplace node.
- Copy the Public IP or reachable Private IP.
- Open a terminal and connect:
ssh <username>@<node-ip>
- Enter the password from the secure password email, or use your private key if you selected an SSH key during creation.
The username depends on the product's base OS. Common usernames include root or ubuntu. Check the product's documentation for the expected login user.
After you connect, the product may display a welcome message or first-run setup instructions. Apply any available OS and application updates before using the node for production.
If the product is a web application, open a browser and go to http://<node-ip> or https://<node-ip> after the node is Running. Make sure the required port is open in the security group.
For a full SSH connection guide including troubleshooting, see Connect to a Linux node.
Common Problems
| Problem | Likely cause | What to do |
|---|---|---|
| No products listed | No enabled marketplace products available for your location, or your account type does not have access. | Try another location, or continue with a CPU node. |
| Product details failed to load | The product detail API returned an error. | Refresh the page. If the error persists, continue with a CPU node and raise a support ticket. |
| Node is Running but the application is not reachable | The port the application uses is not open in the security group. | Check the product's port requirements and update the security group rules. |
| SSH connection fails | TCP 22 is blocked, the node has no reachable IP, or the credentials are wrong. | Check the public IP, security group inbound rules, and the password or SSH key. See Connect to a Linux node. |
Automate This
Use the approved MyAccount API docs for node operations:
- MyAccount API Reference
- Node creation endpoint:
POST /nodes/
The image identifier for a marketplace product and its template ID come from the marketplace product API. Treat unpublished or portal-only fields as implementation details unless they are present in the approved public API documentation.
Related Resources
| Resource | Use it for |
|---|---|
| Create a node | Full node creation reference including all fields and options. |
| Choose a node family | Compare instance families before selecting a plan. |
| Connect to a Linux node | Full SSH connection guide after launch. |
| Connect and use a SQL Server node | Access a Windows SQL Server node after launch. |
| Security Groups | Open or restrict ports for the application. |
| VPC | Use private networking with nodes. |
| Static Public IPs | Manage primary public IPs or Add-on IPs when required. |
| CDP Backups | Back up and restore nodes. |
| SSH Key Management | Create and manage SSH keys. |
Next Step
After the node reaches Running and the application is accessible, apply OS and application updates, and restrict the security group to only the ports your workload needs.