Connect Linode (Akamai) Account
Connect your Linode account to OEC.sh for developer-friendly cloud infrastructure with Personal Access Token authentication.
Note: Linode is now part of Akamai Connected Cloud. The service and API remain the same.
What You'll Get
After connecting your Linode account, OEC.sh can:
| Capability | What It Enables |
|---|---|
| Compute | Auto-provision Linodes (virtual machines) |
| Storage | Use Object Storage (S3-compatible) for backups |
| DNS | Manage DNS records via Linode DNS Manager |
Prerequisites
Before you begin, ensure you have:
- Active Linode account (Sign up here (opens in a new tab))
- Payment method configured
- Email verified
Step-by-Step Connection
Step 1: Access API Tokens
- Log in to cloud.linode.com (opens in a new tab)
- Click your profile icon (top right)
- Click API Tokens
Step 2: Create Personal Access Token
- Click Create a Personal Access Token
- Configure the token:
| Setting | Value |
|---|---|
| Label | OEC.sh Integration |
| Expiry | Never (or your security policy) |
- Set permissions (scroll through all categories):
| Permission | Access Level | Why |
|---|---|---|
| Linodes | Read/Write | Create and manage servers |
| Object Storage | Read/Write | Manage backup buckets |
| Domains | Read/Write | Manage DNS records |
| IPs | Read/Write | Allocate and manage IPs |
| Images | Read Only | List available images |
| Regions | Read Only | List datacenter regions |
| SSH Keys | Read/Write | Manage SSH keys |
| StackScripts | Read Only | Optional for custom scripts |
- Click Create Token
Step 3: Copy Your Token
IMPORTANT: Copy the token immediately - it's only shown once!
The token looks like: 1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Step 4: Add to OEC.sh
- Go to app.oec.sh (opens in a new tab) > Settings > Cloud Accounts
- Click Add Account
- Under API Key Authentication, click Linode (Akamai)
- Fill in the form:
| Field | Value |
|---|---|
| Account Name | Linode Production (or your preferred name) |
| Personal Access Token | Paste your Linode token |
- Click Add Account
Step 5: Verify Connection
- Your Linode account should appear in the list
- Status should show Active (green badge)
- Click the refresh icon to validate
- You should see: Compute, Storage, DNS capability badges
Using Your Linode Account
For Server Provisioning
- Go to Servers > Add Server
- Choose Provision from Cloud
- Select your Linode account
- Choose:
- Region (e.g.,
Newark,Frankfurt,Singapore) - Plan (e.g.,
g6-standard-2,g6-dedicated-2)
- Region (e.g.,
- Click Provision
Linode Plan Types
| Type | Best For | Features |
|---|---|---|
| Shared CPU | General workloads | Cost-effective, burstable |
| Dedicated CPU | Consistent performance | Dedicated vCPU cores |
| High Memory | Memory-intensive apps | Up to 512GB RAM |
| GPU | ML/AI workloads | NVIDIA GPUs |
| Premium | Enterprise | Best hardware, priority support |
Recommended for Odoo
| Use Case | Plan | Why |
|---|---|---|
| Development | g6-nanode-1 | 1GB RAM - basic testing |
| Small Production | g6-standard-2 | 4GB RAM - small teams |
| Medium Production | g6-standard-4 | 8GB RAM - growing usage |
| Large Production | g6-dedicated-4 | Dedicated CPU for consistent performance |
For Backup Storage
- Go to Settings > Storage
- Click Quick Setup on your Linode account
- Choose or create an Object Storage bucket
- Configure backup settings
Note: Linode Object Storage is S3-compatible with free egress to Linodes in the same region.
For DNS Management
- Go to Settings > DNS Providers
- Click Quick Setup on your Linode account
- Select a domain from Linode DNS Manager
- OEC.sh will manage A records automatically
Linode Regions
OEC.sh supports all Linode datacenters:
Core Compute Regions
| Region | Location |
|---|---|
| us-east | Newark, NJ, USA |
| us-central | Dallas, TX, USA |
| us-west | Fremont, CA, USA |
| us-southeast | Atlanta, GA, USA |
| ca-central | Toronto, Canada |
| eu-west | London, UK |
| eu-central | Frankfurt, Germany |
| ap-south | Singapore |
| ap-northeast | Tokyo, Japan |
| ap-west | Mumbai, India |
| ap-southeast | Sydney, Australia |
Distributed Compute (Edge) Regions
Additional edge locations available. Check Linode documentation for the latest list.
Token Permission Details
Minimum required permissions for OEC.sh:
| Permission | Level | Used For |
|---|---|---|
| Linodes | Read/Write | Creating/managing instances |
| Object Storage | Read/Write | Managing backup buckets |
| Domains | Read/Write | Managing DNS zones |
| IPs | Read/Write | Assigning IP addresses |
| Images | Read Only | Listing OS images |
| Regions | Read Only | Listing datacenters |
Optional permissions:
| Permission | Level | Used For |
|---|---|---|
| SSH Keys | Read/Write | Managing SSH keys |
| Firewalls | Read/Write | Cloud firewall management |
| NodeBalancers | Read/Write | Load balancer setup |
Managing Your Connection
Rotate Token
For security, rotate your token periodically:
- Create a new token in Linode Cloud Manager
- Update OEC.sh with the new token
- Delete the old token in Linode
- Recommended: Every 90 days
Revoke Token
If compromised:
- Go to Linode Cloud Manager > API Tokens
- Find the token and click Revoke
- Token is immediately invalidated
- Create a new token and update OEC.sh
Delete Account
- In OEC.sh, click Delete on the account
- Optionally, revoke the token in Linode
Troubleshooting
"Invalid Personal Access Token" Error
Cause: Token is incorrect, expired, or revoked.
Solution:
- Verify the token exists in Linode Cloud Manager
- Check if it has expired (view expiry date)
- Ensure you copied the complete token
- Create a new token if needed
"Insufficient Permissions" Error
Cause: Token lacks required permissions.
Solution:
- Review token permissions in Linode
- You cannot edit existing tokens - create a new one
- Ensure Read/Write on Linodes, Object Storage, Domains
Linode Creation Fails
Cause: Could be account limits, region capacity, or plan issues.
Solutions:
- Limits: New accounts have limits - open a support ticket
- Region: Try a different datacenter
- Plan: Some plans may be unavailable
- Billing: Verify payment method is valid
Object Storage Access Denied
Cause: Token lacks Object Storage permissions or storage not enabled.
Solution:
- Verify token has Object Storage: Read/Write
- Go to Linode > Object Storage and enable it if needed
- Object Storage may require account verification
DNS Zone Not Found
Cause: Domain not in Linode DNS Manager.
Solution:
- Go to Linode > Domains
- Add your domain as a zone
- Update nameservers at your registrar:
ns1.linode.comns2.linode.comns3.linode.comns4.linode.comns5.linode.com
- Refresh connection in OEC.sh
Why Choose Linode?
Advantages
- Developer Focus: Clean UI, great documentation
- Pricing: Simple, predictable pricing
- Network: Premium network, free inbound
- Support: 24/7 human support included
- Akamai Integration: CDN and edge capabilities
Considerations
- Fewer advanced managed services than hyperscalers
- GPU availability may be limited
- Some enterprise features still developing
Cost Considerations
Linode charges monthly with hourly billing:
| Resource | Billing |
|---|---|
| Linodes | Hourly (monthly cap) |
| Object Storage | Per GB stored + outbound |
| Block Storage | Per GB per month |
| Backups | 25% of Linode cost |
| NodeBalancers | Fixed monthly rate |
Cost-saving tips:
- Same-region traffic between Linode services is free
- Object Storage egress to Linodes is free
- Use shared CPU for development workloads
- Enable Backups service (cheaper than DIY)