ClusterWare User Guide
  • 👋Welcome to ClusterWare!
  • Learning Path
    • 🔭Overview
    • 1️⃣Create a distributed NodeJS application in 10 minutes
      • Step 1: Create a new cluster
      • Step 2: Onboard servers to ClusterWare
      • Step 3: Install server software
      • Step 4: Create application instances
      • Step 5: Import application source code
      • Step 6: Start the application
      • Step 7: Create and start application load balancer
    • 2️⃣Uniformly secure access to your infrastructure
      • Step 1: Create Security Policy
      • Step 2: Install Firewall
      • Step 3: Apply Security Policies
    • 3️⃣Secure the data in-transit with SSL
      • Step 1: Gateway Security
      • Step 2: Endpoints Security
    • 4️⃣Eliminate a single point of failure in 10 minutes
      • Step 1: Onboard a new server
      • Step 2: Install Niginx
      • Step 3: Configure DNS
      • Step 4: Create and start the failover load balancer
      • Step 5: Run a load balancer outage experiment
  • Fundamentals
    • 🧩Sync, Insights, Tasks
    • 🤖Supported Technologies
    • 🛡️Server Authentication Methods
    • 💡Connectivity Troubleshooting
  • Services
    • Clusters
      • Cluster Selection & Creation
      • Editing Cluster
      • Notification Subscriptions
      • Auto-deployment (CI/CD)
    • Dashboard
      • Load Balancers & Applications
    • Servers
      • Create/Edit Server
      • Status
      • Software
      • Security
        • Enabling Non-Root Firewall Status Checking
        • Changing Firewall Status
        • Applying Security Policies
      • Metrics
      • Alerts
    • Applications
      • Create/Edit Application
      • Status
      • Git
      • Output Log / Error Log
      • Metrics
      • Alerts
    • Load Balancing
      • Create/Edit Load Balancer
      • Status
      • Gateway Security
      • Endpoint Security
    • Security Policies
      • Create/Edit Security Policy
Powered by GitBook
On this page
  • Overview
  • Key Sections
  • Name
  • Host / Port
  • Authentication
  • Alerts & Metrics
  • Connecting to the server
  1. Services
  2. Servers

Create/Edit Server

PreviousServersNextStatus

Last updated 10 months ago

Overview

Key Sections

Name

The user-defined name for the server. You can choose to click on the dice button on the right to choose a random name.

To maintain a consistent naming convention you can chose to use the server name generated by ClusterWare and create a DNS alias (CNAME) pointing to the IP address of the server.

Host / Port

The IP address or hostname of the server with the port number for SSH connections. By default the port is set to 22 but you can overwrite this value with your custom port number on which your server listens to SSH connections.

Authentication

Public Key authentication - Generate new SSH keys

This option is selected by default when you create a new server. This way ClusterWare generates a new unique key pair that will be used to secure the communication with your server.

Public Key authentication - Use own SSH keys

Use this option to provide your own SSH keys instead of the ClusterWare generated keys. You may want to use this option when you have a dedicated key pair already configured on the server to use with ClusterWare.

For security reasons ClusterWare recommends the key pairs to have single purpose. For example to use one key pair for ClusterWare only and the other kay pair not shared with ClusterWare to use for other purposes.

ClusterWare supports ED25519 and ECDSA keys only in OpenSSH format. RSA keys are no longer allowed for security reasons.

Public Key authentication - Don't change SSH keys

This option is selected by default when you edit an existing server. This prevents accidental change of the access keys when you modify other settings of the server.

Password based authentications (not recommended)

To use the password based authentication click on the Password/Public Key toggle and provide the password in the text field below.

Alerts & Metrics

CPU Usage

Memory Usage

Disk Usage

Security Checks

Enable or disable automatic security checks whether

Connecting to the server

When you save the server settings, the Console will display the instructions needed to onboard the server to ClusterWare. It includes just two simple steps to authorize the unique SSH Public Key and let ClusterWare systems access your server.

Once you complete the instructions displayed on the screen, click Done - Sync Server Status button to initiate the first sync. If the server card shows CPU and Memory stats for the server, you have onboarded the server successfully!

You can also access the instructions by clicking on the Connect button in the bottom right corner of the server card.

If you followed the instructions from the Console and still experience connectivity issues, consult the Connectivity Troubleshooting guide.

Toggle on/off, and specify a percentage above which should be triggered.

Toggle on/off, and specify an amount in MB above which should be triggered.

Toggle on/off, and specify an amount in MB above which should be triggered.

If any of the above checks fail, ClusterWare will generate a security .

Security Checks feature works only if you have enabled on the server.

🛡️Server Authentication Methods
alerts
alerts
alerts
alert
💡Connectivity Troubleshooting
Firewall non-root status checking