IBM Cloud Docs
Configuring virtual servers

Configuring virtual servers

When you have access to your virtual server, make sure that you change your password and consider setting up SSH for a more secure authentication solution. You have many other options for configuring your virtual server to meet the needs of your environment.

Before you configure a virtual server, review your options for connecting to the server and how to manage passwords and credentials. For more information, see Getting started with IBM Cloud Virtual Private Networking and Managing device access.

Log in

Log in to the IBM Cloud® console with the credentials that you received in an email when your account was initially created.

Locate your virtual server

Find your virtual server in the Device List in the IBM Cloud console. From the Device List, you can manage devices, upgrade devices, or generate bandwidth usage charts. For more information, see Managing virtual servers.

Change your password

Change your password by using strong password guidelines. See Viewing and managing device usernames and passwords.

Manage SSH keys

SSH provides a better security solution than password authentication. See Getting started with SSH keys.

Record IP addresses and credentials

Keep a log of IP addresses and credentials for the server in a safe location so that you can access them quickly without having to log in to the IBM Cloud console.

  • Individual device IP addresses can be viewed from the Device List.
  • Individual device root passwords can be viewed in the device’s Snapshot View. Click the arrow next to the device name to expand the view.
  • Multiple device IP addresses can be viewed by using the Download CSV action within the Device List. Select Download CSV from the Settings cog to download a full list of devices and details in spreadsheet format.

Update software credentials

All software that was loaded onto your device during the provisioning process was assigned temporary credentials. These credentials are viewed and managed on the Passwords tab of each device in the IBM Cloud console. Use these temporary credentials to access your software for the first time. As a best practice, change the password to your software after you access it for the first time. Use a strong password that consists of a combination of letters, numbers, and symbols.

Optionally, password updates can be stored on the Passwords tab for each device. However, understand that when you store passwords within the IBM Cloud console, any person with access to the account and appropriate permissions can view passwords that are stored on the Passwords screen.

For more information about viewing and managing your software credentials, see Managing classic infrastructure access.

Access your server on the private network

The private network is the precursor to interacting with your devices through remote desktop (RDP) by using SSH and KVM over IP. The VPN Access tool allows for private network connection to either the closest SSL VPN endpoint or to the endpoint of your choice. VPN access is also required to interact with several services that are offered. For more information, see Getting started with Virtual Private Networks (VPN).

Set up monitoring

Monitoring is primarily used as a resource to check your server’s uptime, but it can also be useful for knowing when to scale. IBM Cloud Monitoring services are available to cover various monitoring needs. Standard Monitoring, sometimes referred to as “Basic Monitoring,” is generally used in the ping-and-respond method by using either a slow or service ping that is initiated by using the IBM Cloud console. IBM Cloud Monitoring keeps you aware of any issues with your devices. IBM Cloud Monitoring gives you insight into the performance and health of your applications, services, and platforms. Your administrators, DevOps teams, and developers have a full-stack telemetry with advanced features to help them monitor and troubleshoot, define alerts, and design custom dashboards. For more information, see IBM Cloud Monitoring.

Configure security groups

You can use security groups to limit network traffic on your virtual servers. Use security groups to enact a set of IP filter rules that define how to handle incoming and outgoing traffic to both the public and private interfaces of a virtual server instance. For more information, see Getting started with security groups.

Configure firewalls

Hardware firewalls are also available for even more protection. Hardware firewalls are provisioned on demand with no downtime. If rules are established properly, a firewall can protect your server from unwanted activity. After you order a firewall, it must be enabled and rules must be set.

For more information, see the following information.

Schedule backups

Backups make sure that your data is safely stored outside of your device and protected if it is lost. The following backup services are available to store your data in a secure location in case you ever need to reload your information onto your device:

  • IBM Cloud Backup for Classic is an automated, agent-based backup system. This backup system is a popular “set-and-forget” solution for managing your device. It is compatible with Microsoft software that includes Exchange and SQL through extra plug-ins. IBM Cloud Backup for Classic users interact with this service through IBM Cloud Backup for Classic’s WebCC web-based application. For more information, see Getting started with IBM Cloud Backup for Classic services.
  • R1Soft® Continuous Data Protection is backup software that can be installed on your server or self-managed virtual machine. It is recommended if you want a single interface to manage all of your backups. You interact with R1Soft® CDP through your proprietary management system, which allows agents to be installed on virtual machines and offers database plug-ins for extra functions. For more information about R1Soft® CDP backup services, see the R1Soft® Documentation.

Next steps

After your virtual server is configured, you can start managing it. For more information, see Managing your virtual server.