Network
The Network API manages private networks and security groups used by compute instances.
Networking in redu.cloud allows you to:
- Create isolated private networks
- Attach instances to networks
- Control traffic using security groups
- Enable or restrict public access
Concepts
Private Network
A private network allows instances to communicate internally.
Each network:
- Has a unique
id - Belongs to a project
- Contains one or more subnets
- Is isolated from other projects
Instances must be attached to at least one private network.
Subnets
Subnets define IP ranges inside a network.
The Network API returns subnet IDs, which are internally managed.
Security Groups
Security groups act as virtual firewalls.
They define:
- Allowed inbound traffic (ingress)
- Allowed outbound traffic (egress)
- Protocol and port restrictions
- Optional IP range restrictions
Each instance can attach multiple security groups.
See Security Groups for details.
Public Access
Instances are public by default.
When an instance is created, it can be accessed through:
- A generated DNS endpoint
- A user-assigned domain name (if configured)
Public access can be disabled when creating an instance (for example, for a private database or internal service).
When public access is disabled:
- No public DNS endpoint is exposed
- The instance remains reachable only inside its private network
Security groups must allow the required ports (for example, 22 for SSH or 443 for HTTPS).
Endpoints
Authentication
All Network API endpoints require an API key:
x-api-key: YOUR_API_KEYSee Authentication for usage examples.