VPCs & Subnets
Isolated private networks with full control of IP addressing.
View Service DetailsA Virtual Private Cloud (VPC) is an isolated layer-2/layer-3 network that belongs entirely to your organization. Traffic in one VPC is invisible to every other tenant — isolation is enforced in the network virtualization layer on every node, not by shared firewall rules.
Building Blocks
| Component | Role |
|---|---|
| VPC | The isolated network container with a private CIDR (e.g. 10.0.0.0/16) |
| Subnet | A segment of the VPC CIDR where VM interfaces live (e.g. 10.0.1.0/24) |
| Virtual Router | Distributed router connecting subnets and providing the default gateway |
| Security Group | Stateful allow-rules attached to VM interfaces |
| Elastic IP | Public IPv4 address mapped to a VM or load balancer |
Designing Your Address Plan
- Use one VPC per environment (production, staging) rather than one giant network
- Pick non-overlapping CIDRs across VPCs and your on-premises networks — overlaps block VPN routing later
- Separate tiers into subnets: e.g. 10.0.1.0/24 web, 10.0.2.0/24 app, 10.0.3.0/24 data
- Leave room to grow: a /16 VPC holds 256 /24 subnets
DHCP and DNS
Each subnet runs a built-in DHCP service that assigns addresses from its range; you can also reserve fixed IPs per VM. Internal DNS resolves VM names within the VPC, and you can point subnets at your own DNS servers instead.
bash
# Create a VPC and a subnet via API
curl -X POST "https://api.daakyicloud.com/v1/vpcs" \
-H "Authorization: Bearer $TOKEN" \
-d '{"name": "prod-vpc", "cidr": "10.0.0.0/16", "region": "accra-1"}'
curl -X POST "https://api.daakyicloud.com/v1/vpcs/vpc-9d1c/subnets" \
-H "Authorization: Bearer $TOKEN" \
-d '{"name": "web-tier", "cidr": "10.0.1.0/24", "gateway": "10.0.1.1"}'Two VPCs can be connected with VPC peering (Networking → Peering) when workloads in different VPCs need to talk privately — routes are exchanged automatically.