NEW? Start Here: Your First 30 Minutes on InMotion Cloud
Updated August 4, 2026 by Sean Perryman
6 Minutes to Read
Welcome to InMotion Cloud. This guide walks you through everything you need to launch and connect to your first virtual machine (VM), also called an instance. You'll be up and running in about 30 minutes.
You can complete all tasks through either the web-based Horizon dashboard or the command-line interface (CLI). Both options accomplish the same thing—choose whichever fits your workflow. This guide shows both methods so you can pick the one that works best for you.
Getting Help
Our support team is here to help you succeed. If you get stuck at any point, don't hesitate to reach out.
Ways to contact support:
Pro tip: If you're brand new, try opening a quick "Hello, testing the support system!" ticket just to see how it works. Our team will respond and confirm everything is set up correctly.
- Support Tickets: Log into InMotion Central and click Support in the left menu to open a ticket.
- Live Chat: Available 24/7 from within InMotion Central.
- Phone: Call our support line for immediate assistance.
Accessing Your Horizon Dashboard
Your Horizon dashboard is the control center for your InMotion Cloud environment. From here, you manage instances, networks, storage, and security.
To access Horizon:
- Log into InMotion Central (your billing and project portal).
- Click Projects in the left navigation menu.
- Find your Cloud Project and click the project name.
- Click the Login to Horizon button.
You're now in the Horizon dashboard. The left sidebar shows all available services organized by category (Compute, Network, Storage, etc.).
Launching Your First Instance
An instance is a virtual machine running in your cloud environment. You'll configure the instance size (flavor), operating system (image), and network during creation.
Using Horizon Dashboard
To launch an instance in Horizon:
- Details: Enter an instance name (e.g., "web-server-01"). - Source: Select an image (Ubuntu 22.04, CentOS Stream 9, etc.). Choose "Boot from image" as the boot source. - Flavor: Choose your instance size based on CPU/RAM needs (e.g., "m1.small" for testing). - Networks: Select your project network (typically named "project-net" or similar).
- Navigate to Project > Compute > Instances in the left sidebar.
- Click Launch Instance in the upper right.
- Complete the required tabs in the launch wizard:
- Key Pair tab (recommended): Click "Create Key Pair" to generate SSH keys for secure access. Save the private key file to your local machine.
- Click Launch Instance at the bottom right.
Your instance will appear in the instances list with a "Build" status. After 1-2 minutes, the status changes to "Active" and shows a power state of "Running".
Using CLI
To launch an instance via CLI:
First, install and configure the CLI tools on your local machine. You'll need your RC file from Horizon (navigate to Project > API Access > Download OpenStack RC File).
1# Source your credentials2source ~/your-project-openrc.sh34# Launch an instance5openstack server create \6 --image "Ubuntu 22.04" \7 --flavor m1.small \8 --network project-net \9 --key-name my-keypair \10 web-server-011112# Check status13openstack server show web-server-01 -f value -c status
Wait for the instance status to change from "BUILD" to "ACTIVE".
Understanding Default Usernames
Cloud images come pre-configured with a default system user for SSH access. The username depends on your chosen operating system.
Default usernames by OS:
- Ubuntu: ubuntu
- CentOS Stream: centos
- Debian: debian
- AlmaLinux: almalinux
- Rocky Linux: rocky
- Fedora: fedora
You cannot log in as the root user directly via SSH. Instead, log in with the default username and use sudo for administrative tasks.
Allocating a Floating IP
Your instance has a private IP address on your project network. To access it from the internet or your local network, you need a floating IP (a public IP address).
Using Horizon Dashboard
To allocate and assign a floating IP:
- Navigate to Project > Compute > Instances.
- Find your instance in the list.
- Click the dropdown arrow next to "Create Snapshot" and select Associate Floating IP.
- If you don't have a floating IP allocated, click the + button next to "IP Address".
- Select the external network pool (typically "public" or "ext-net").
- Click Allocate IP.
- Select the newly allocated IP from the dropdown.
- Click Associate.
Your instance now shows both its private IP and the newly assigned floating IP. Use the floating IP for SSH connections.
Using CLI
To allocate and assign a floating IP via CLI:
1# Allocate a floating IP from the public pool2openstack floating ip create public34# Associate it with your instance5openstack server add floating ip web-server-01 203.0.113.45
Replace 203.0.113.45 with your actual allocated floating IP address.
Opening Your Security Group
InMotion Cloud blocks all inbound traffic to instances by default. You must create security group rules to allow SSH access and any other services you plan to run.
Using Horizon Dashboard
To allow SSH access:
- Rule: Select "SSH" from the dropdown. - Remote: Select "CIDR" to allow access from specific IPs, or "Any" for worldwide access. - CIDR: Enter your IP address in CIDR notation (e.g., "203.0.113.50/32") or leave as "0.0.0.0/0" for any IP.
- Navigate to Project > Network > Security Groups.
- Find the "default" security group and click Manage Rules.
- Click Add Rule in the upper right.
- In the Add Rule dialog:
- Click Add.
The rule appears in your security group. Repeat this process to add rules for HTTP (port 80), HTTPS (port 443), or custom application ports.
To allow ping/ICMP (recommended for troubleshooting):
- Click Add Rule again.
- Rule: Select "All ICMP".
- Direction: Ingress.
- Remote: CIDR (0.0.0.0/0 or your specific IP).
- Click Add.
Using CLI
To create security group rules via CLI:
1# Allow SSH (port 22)2openstack security group rule create default \3 --protocol tcp --dst-port 22 --remote-ip 0.0.0.0/045# Allow HTTP (port 80)6openstack security group rule create default \7 --protocol tcp --dst-port 80 --remote-ip 0.0.0.0/089# Allow ICMP (ping)10openstack security group rule create default \11 --protocol icmp --remote-ip 0.0.0.0/0
For production environments, restrict access to specific IP ranges instead of 0.0.0.0/0.
Connecting to Your Instance
Now that your instance has a floating IP and SSH access is allowed, you're ready to connect.
Option A: Web Console (No SSH Required)
If you prefer not to use command-line tools, you can access your instance directly through the Horizon dashboard:
- Navigate to Project > Compute > Instances.
- Click on your instance name.
- Go to the Console tab.
- Click in the console window and log in with your default username.
This browser-based console works without any local software. It's great for quick checks or if you're not comfortable with SSH.
Option B: SSH (For Technical Users)
If you're comfortable with the command line, SSH provides a faster, more powerful connection.
To connect via SSH:
1ssh -i ~/path/to/my-keypair.pem ubuntu@203.0.113.45
Replace ubuntu with the correct default username for your OS, my-keypair.pem with your key file path, and 203.0.113.45 with your floating IP address.
If connection fails, troubleshoot:
- Verify the security group allows SSH (port 22) from your IP.
- Confirm you're using the correct default username for your OS.
- Check that your instance status is "Active" and power state is "Running".
- Test connectivity with
ping 203.0.113.45to verify network access.
Updating Your Server
After connecting, update your instance to the latest security patches and software versions. This is critical for security and stability.
For Ubuntu/Debian:
1sudo apt update && sudo apt upgrade -y
For CentOS/AlmaLinux/Rocky Linux:
1sudo dnf update -y
If prompted to reboot, wait 1-2 minutes and reconnect. Your instance is now fully updated and ready for application deployment.
Next Steps
You've successfully launched and configured your first InMotion Cloud instance. Here's what to explore next:
Recommended articles:
Questions? Our support team is always here to help. Open a ticket anytime from InMotion Central.
- Install software: Deploy web servers (Apache, Nginx), databases (MySQL, PostgreSQL), or application frameworks.
- Create snapshots: Back up your instance before making major changes.
- Set up block storage: Add volumes for persistent data storage.
- Configure load balancing: Distribute traffic across multiple instances.
- Explore networking: Create private networks, routers, and VPNs.
- How to Access the OpenStack Horizon Dashboard
- Managing Instance Network Interfaces
- Creating Instance Snapshots
- Booting Instances from Volumes
Welcome to InMotion Cloud. You're ready to build.
Sean Perryman
Technical Account Engineer
Sean Perryman is a Technical Account Engineer at InMotion Cloud, where he helps organizations design, deploy, migrate, and support mission-critical workloads in the cloud. Working closely with customers throughout the entire lifecycle of their environments, he specializes in solving complex infrastructure challenges while ensuring platforms remain secure, reliable, and scalable.