VPC in Cleura Cloud

Virtual Private Cloud (VPC)

A Virtual Private Cloud (VPC) in Cleura Cloud gives you a secure, isolated environment for your workloads. Define your own IP ranges, subnets, and routing while maintaining full control over how your services communicate both internally and externally. Each VPC operates within its own logical network, providing predictable performance, compliance-ready boundaries, and the flexibility to design multi-tier or hybrid architectures.

Isolated and configurable networks

Every project in Cleura Cloud includes a dedicated virtual network layer. You decide how to structure it: create subnets, define address spaces, and connect instances using internal or external routing. Each subnet is backed by managed DHCP and DNS, enabling smooth configuration of IP allocation and name resolution without external dependencies.

Routing and connectivity

Use virtual routers to connect subnets, define gateways, or enable NAT for controlled outbound access. Public connectivity is achieved through floating IPs, allowing specific resources, such as load balancers or bastion hosts, to be reachable from the internet while keeping the rest of the network private. For hybrid use cases, standard site-to-site IPsec VPN or partner interconnect options make it easy to extend your on-premise environments into Cleura Cloud.

Security and access control

Security groups provide stateful filtering at instance or port level. You define the inbound and outbound rules (by CIDR, protocol, and port) to enforce least-privilege principles and protect workloads from unnecessary exposure. Combined with project-level isolation and role-based access control, this forms a strong foundation for compliance and governance.

Flexible designs for every workload

A single VPC can host complex topologies such as three-tier web applications, data platforms, or shared-service networks. You can distribute subnets across availability zones, attach multiple interfaces to instances, or build patterns for larger environments. With full API, CLI, and Infrastructure-as-Code support, every configuration can be versioned and deployed consistently across projects and regions.

Integration with other networking features

VPCs form the foundation for all networking in Cleura Cloud, interconnecting seamlessly with Routers, Floating IPs, Load Balancers, and Security Groups. This allows you to isolate environments while maintaining flexible routing and controlled exposure of workloads. All network segmentation and traffic control remain confined to Cleura’s European regions.


What is a Virtual Private Cloud?

A Virtual Private Cloud (VPC) is an isolated, software-defined network within Cleura Cloud where you define IP ranges, subnets, routing, and security for your workloads.

How does Cleura ensure network isolation?

Each VPC operates within its own logical network. Traffic between projects or VPCs is blocked by default unless you explicitly configure routing between them.

How do I connect my VPC to the internet?

Public access is enabled through floating IPs assigned to selected resources, such as load balancers or bastion hosts. This lets you expose services without opening the entire network.

Can I connect my VPC to an on-prem environment?

Yes. You can establish site-to-site IPsec VPN connections or use a partner interconnect to extend your on-premise network into Cleura Cloud.

What’s the difference between subnets and security groups?

Subnets define the internal IP layout and routing scope, while security groups control traffic to and from instances or ports using stateful rules.

Can I automate network configuration?

Yes. All network components, such as routers, subnets, and security groups, can be created and managed via the API, CLI, or Infrastructure-as-Code tools.

Where is network traffic processed?

All network segmentation and traffic control remain within Cleura’s European regions.

CONTENTS