This guide walks you through creating a Compute Instance in a core compute region using Cloud Manager. If you wish to create a Compute Instance in a distributed compute region, see Create a Compute Instance in a Distributed Compute Region.

To create a Compute Instance, you will:

1. Open the Create form in Cloud Manager
2. Select a region
3. Choose a distribution, app, or image
4. Choose a plan
5. Set the label, add tags, and assign to a placement group
6. Create a password and add SSH keys
7. Enable or disable disk encryption
8. Assign to a VPC (optional)
9. Assign to a Cloud Firewall (optional)
10. Assign to a VLAN (optional)
11. Configure additional options
12. Add user data
13. Deploy the Compute Instance

Open the Create form in Cloud Manager

Log in to Cloud Manager, click the Create dropdown menu on the top bar, and select Linode. This opens the Create form.

Select a region

Next, you must select the region where the Compute Instance will reside. Regions correspond with individual data centers, each located in a different geographical area. You should likely select the region closest to you and/or your customers. This helps reduce latency and can make a significant impact in connection speeds and quality. If you wish to make use of a particular product or service, you may also wish to verify that the product is available within your desired data center.

You need to select a region before selecting your plan type. Pricing may vary between data centers. The following resources will help you choose a data center.

• Global infrastructure map
• Speed tests for data centers
• Choosing a data center (guide)

Choose a distribution, app, or image

One of the first steps to deploy a Compute Instance is to decide what you actually wish to deploy. You're able to select a Linux distribution for a barebones install, a Marketplace App with your desired software, and a few other options.

• Distributions: Select from any supported Linux distribution. This option lets you start with a stable Linux operating system and build your own software stack from scratch. Popular distributions include the latest LTS releases of Ubuntu, Debian, CentOS Stream, RHEL-derivatives (such AlmaLinux and Rocky Linux), and more. Each distribution comes with its own set of preinstalled software and commands. See Choose a Linux distribution for a full list of distributions.

• Marketplace: Select from the many Apps currently featured in Marketplace. This installs and configures your desired software, allowing you to start using your applications right away. Popular apps include Wordpress, WooCommerce, LEMP, cPanel, Plesk, and Nextcloud. See Marketplace Apps - Get started.

• StackScripts: Select from any StackScripts previously created on your account or from a community StackScript. StackScripts automate the deployment of software and configuration by executing commands within your system after the first boot. See Deploy a Compute Instance using a StackScript.

• Images: Select from any Custom Image or Recovery Image stored on your account. Recovery Images are generated after a Compute Instance has been deleted and Custom Images can be created based on existing Compute Instances or image files. See Get started with custom images.

• Backups: If you have the Backups service enabled on an existing Compute Instance, you can select any available backup snapshot to deploy from. See Restore a backup to a new Compute Instance.

• Clone Linode: Creates a new Compute Instance from the disks and configuration on an existing Compute Instance. See Clone a Compute Instance.

This guide assumes you are creating a Compute Instance from a Distribution. If you select a different option, you may wish to follow the specific instructions within their own corresponding guides.

Choose a Compute Instance type and plan

There are several different Compute Instance types and plan sizes, each with a preset amount of hardware resources (such as vCPU cores, memory, and storage space). Review the Choose a Compute Instance plan guide for advice on selecting the best plan for your needs, application’s requirements, and pricing considerations. Note that pricing and plan options may vary between data centers.

📘

You can resize to a different plan size or Compute Instance type at any time. This means your aren't locked in to whichever plan you select here. See Resize a Compute Instance for instructions.

Set the label, add tags, and assign to a placement group

• Label: The label is the name of the Compute Instance, allowing you to easily identify it from other Compute Instances. A good label should provide some indication as to what the Compute Instance is used for. As an example, a label of acme-web-prod may indicate that the Compute Instance is the production website for the company Acme. If you have already implemented your own naming conventions for your cloud infrastructure, follow those conventions. Labels must only use letters, numbers, underscores, dashes, and periods.

• Tags: Adding tags gives you the ability to categorize your services however you wish. If you're a web development agency, you could add a tag for each client you have. You could also add tags for which services are for development, staging, or production.

• Placement Groups: (Optional) Add this Compute Instance to a placement group to manage its physical location in a data center ("region"). Placement groups can be set up to group your Compute Instances close together to help with performance, or further apart to support high availability. Placement groups are available at no additional cost, but they're not available in all regions. See Work with placement groups to learn more.

📘

If you don't have a placement group

Click Create Placement Group to create one. This takes you to a separate interface, outside creating your Compute Instance. For ease of use, create your Compute Instances in a supported region, then later create a placement group and assign your Compute Instances to it.

Create a password and add SSH keys

• Root Password: The password used to log in to the system as the root user. The root user is the main account and has access to the entire system, including files and commands. This password should be extremely strong to prevent attackers from gaining access to your system. By default, the root user can log in over Lish and SSH using this password, though we do recommend disabling this in the Set up and secure a Compute Instance guide.

• SSH Keys: Add any SSH Keys to the root user account on the server. This enables you to log in through SSH without needing a password. SSH keys are created as a pair: a private key stored on your local computer and a public key that you can upload to remote systems and services. Since you only share your public key and your private key is kept safe and secure, this is a much more secure method for authentication than passwords. Learn more about uploading SSH keys through Cloud Manager on the Manage SSH keys guide.

Enable or disable disk encryption

Consider enabling Encrypt Disk on this Compute Instance. The platform manages encryption and decryption for you. After a compute instance is created, use Rebuild to change this setting.

📘

Limited availability

Disk Encryption is not currently available in all regions.

More information is available from the Local Disk Encryption guide.

Assign to a VPC (optional)

Consider using a VPC (Virtual Private Network) to isolate your new Compute Instance from other systems on the Akamai cloud computing platform and the internet. This adds an additional layer of privacy and can be used alongside Cloud Firewalls. If you are not sure you need a VPC, you can skip this step. You can add this new Compute Instance to a VPC at any time in the future by following the steps within the Assign a Compute Instance to a VPC guide.

• Select VPC: To assign this Compute Instance to a VPC, select the VPC from the Assign VPC dropdown menu. If you do not yet have a VPC in the selected data center, click the Create a VPC button and follow the instructions on the Create a VPC guide.

• Select Subnet: A Compute Instance can be assigned to a single subnet, which lets you further segment traffic and services within a VPC. Select the desired subnet within the Subnet dropdown menu.

• Auto-Assign IPv4 address: By default, an IPv4 address will be automatically generated for the Compute Instance on the subnet’s defined CIDR range. If you want to manually assign an IP address, uncheck the Auto-assign a VPC IPv4 address for this Linode option and enter your custom IPv4 address. This address must still be within the subnet’s IP range.

• Public IPv4 address: If you wish to enable public internet access on this new Compute Instance, check the Assign a public IPv4 address for this Linode option. By default, this is unchecked and you will not be able to access the internet from this Compute Instance.

• Additional IPv4 ranges: You can assign additional IPv4 ranges that can be used to reach this Compute Instance and/or the services running on it. For example, you may wish to assign additional IPv4 ranges to directly expose Docker containers to the VPC.

For additional information and considerations, review the Assign a Compute Instance to a VPC guide.

Assign to a Cloud Firewall (optional)

To protect your new Compute Instance from unwanted traffic, consider using a Cloud Firewall. This lets you cascade firewall rules across multiple services and manage those rules within Cloud Manager, Linode CLI, and Linode API.

To assign your Compute Instance to a Cloud Firewall, select the firewall from the Assign Firewall dropdown menu. If you do not have a firewall or wish to create a new one, click the Create Firewall link and follow the instructions within the Create a Cloud Firewall guide. You can always skip this step and assign a firewall at a later time by following the instructions in the Apply firewall rules to a service guide.

Assign to a VLAN (optional)

Add this Compute Instance to a secure private network. VLANs are available at no additional cost, though not all data centers currently support this feature. See VLANs to learn more.

🚧

Consider using a VPC instead of a VLAN

In most cases, it's recommended to use a VPC over a VLAN. VPCs operate on a higher network layer and come with more IP addressing and IP routing functionality. Additionally, you can further segment out network traffic through subnets, each of which has its own CIDR range. Review these differences to learn more.

Configure additional options

The following features and services can be configured during the Compute Instance's creation or at any point after.

• Add the Backups service: Safeguard your data with the Backups service, enabling automatic backups of the disks on your Compute Instances. Up to four backups are stored as part of this service, including automated daily, weekly, and biweekly backups in addition to a manual backup snapshot. See Backups to learn more and view pricing.

• Add a private IP: A private IP gives you access to the data center's private network. This enables you to communicate with other Compute Instances with private IPs in the same region without using a public IPv4 address. Private IPs are needed to configure your Compute Instance as a NodeBalancer back end. The private IP feature requires a Public Internet network interface. As such, Compute Instances configured with both VPCs and a private IP address are configured with the VPC network interface on eth0 and the Public Internet interface on eth1.

  🚧

  Consider using a VPC instead of the private IP address feature

  Private IP addresses are accessible by any other Compute Instance in the same data center, provided that Compute Instance also has a private IP. To further isolate your Compute Instance, consider using a VPC instead. Review these differences to learn more.

Add user data

User data can be provided to the Metadata service, which is then consumed by cloud-init when your Compute Instance boots up for the first time. For information on the Metadata service, user data formats, and our cloud-init integration, see Metadata Service.

Deploy the Compute Instance

Confirm the details for this Compute Instance within the Linode Summary section. Once you are satisfied, click Create Linode to start the deployment process. This process can take anywhere from 3 minutes for Distribution Images to up to 30 minutes for some Marketplace Apps. After the creation process has started, you are automatically redirected to the detail page for this Compute Instance. From here, you can follow the status as the Compute Instance is deployed as well as see information about the new Compute Instance, such as the IP addresses.

Next steps

Once the Compute Instance has been created and is done initializing, you can start configuring and using it. Follow Set up and secure a Compute Instance for guidance on connecting your Compute Instance, performing any initial configuration steps on your Linux system, and securing your server.

🚧

Email restrictions on our Platform

In an effort to fight spam originating from our platform, outbound connections on ports 25, 465, and 587 are blocked by default on Compute Instances for some new accounts. These restrictions prevent applications from sending email. If you intend to send email from a Compute Instance, see Send email on the Linode platform to learn more about our email policies and to request the removal of these restrictions.