Linode

Authentication

Linode (Akamai Cloud) uses a personal access token. Generate one from the Linode Cloud Manager with read/write access to Linodes, SSH Keys, and Regions.

Field	Required	Description
api_token	Yes	Personal access token from Linode Cloud Manager

Configuration

providers:
  linode:
    api_token: "${LINODE_TOKEN}"
    region: us-east
    image: linode/ubuntu22.04
    size: g6-nanode-1

defaults:
  provider: linode

Regions

Linode uses descriptive region IDs:

Slug	Location
us-east	Newark, NJ
us-central	Dallas, TX
us-west	Fremont, CA
us-southeast	Atlanta, GA
eu-west	London, UK
eu-central	Frankfurt, Germany
ap-south	Singapore
ap-southeast	Sydney, Australia
ap-northeast	Tokyo, Japan
ca-central	Toronto, Canada

Run managed providers regions linode to list all available regions.

Sizes

Linode instance types use a generation-based naming scheme:

Slug	Specs
g6-nanode-1	1 vCPU, 1 GB RAM, 25 GB disk
g6-standard-1	1 vCPU, 2 GB RAM, 50 GB disk
g6-standard-2	2 vCPU, 4 GB RAM, 80 GB disk
g6-standard-4	4 vCPU, 8 GB RAM, 160 GB disk
g6-standard-6	6 vCPU, 16 GB RAM, 320 GB disk

Run managed providers sizes linode --region us-east to list all available types.

Images

Linode images use a linode/ prefix:

Slug	OS
linode/ubuntu22.04	Ubuntu 22.04 LTS
linode/ubuntu24.04	Ubuntu 24.04 LTS
linode/debian12	Debian 12

Auto storage

Linode does not support auto-provisioned storage. Configure S3-compatible storage manually in managed.yaml if your services need backup storage:

storage:
  endpoint: "s3.us-east-1.amazonaws.com"
  region: "us-east-1"
  bucket: "my-backups"
  access_key: "${S3_ACCESS_KEY}"
  secret_key: "${S3_SECRET_KEY}"

You can also use Linode's own Object Storage by providing its endpoint (e.g. us-east-1.linodeobjects.com) and creating access keys manually in the Cloud Manager.

Networking

Linode assigns both public and private (VLAN) IPv4 addresses. Managed uses the private IP for inter-server communication when servers are in the same region.