Public IP Address
A Public IP Address allows your resources in CloudRaya to be reachable from the internet.
Public IPs are standalone networking resources that can be attached to different types of services, such as Virtual Machines, VPC routers, Load Balancers, and Kubernetes clusters.
What Is a Public IP in CloudRaya?
In CloudRaya, a Public IP:
- Is a routable IP address accessible from the internet
- Is scoped to a single Cloud Zone
- Exists independently from compute resources
- Can be attached, detached, or retained based on usage
A Public IP does not always belong to a VM.
It can exist even when not currently attached to any instance.
Where Public IPs Are Used
Public IPs in CloudRaya may be attached to:
-
Virtual Machines
To expose services such as SSH, HTTP, HTTPS, or application ports
-
VPC Virtual Routers
Used as the gateway IP for:
- VPN connections
- VPC routing
-
Load Balancers
To provide a single public entry point for multiple backend VMs
-
Kubernetes Clusters
For cluster access, ingress controllers, or exposed services
Because of this, the Public IP list can contain IPs associated with different service types.
Viewing Public IPs
You can view and manage Public IPs from:
Dashboard → Network → Public IP Address
This page displays all Public IP addresses owned by your project, including:
- IP address
- Attached object type (VM, Virtual Router, Load Balancer, Kubernetes)
- Instance name (if applicable)
- Region / Cloud Zone
- Current status
Some Public IPs may show no instance attached. This is expected behavior.
Managing Public IP Addresses
You can acquire, attach, detach, or release Public IP addresses using the CloudRaya Control Panel.
📄 See:
Public IP Without an Instance
A Public IP may appear without an attached instance when:
- A VM was deleted but the Public IP was retained
- The IP is reserved for future use
- The IP was previously attached to a service that has been removed
- The IP is temporarily unattached
These Public IPs remain billable and available for reuse.
You can later attach them to supported services if needed.
Public IP Limits
By default, each account can have up to 4 Public IP addresses in total.
This means:
- The Public IP limit is applied at the account level, not per project
- Public IPs are shared across all projects under the same account
- Creating a Public IP in one project reduces the remaining quota for other projects
Public IP Lifecycle
A Public IP can be:
- Automatically assigned during resource creation
- Detached and retained
- Reattached to supported services
- Deleted when no longer needed
Important notes:
- Public IPs cannot be deleted if they are actively used by certain services
- Some Public IPs are required system components (for example, VPC routers)
Billing Behavior
Public IPs are billed based on usage:
- Attached Public IPs are billed as part of their service
- Retained (unused) Public IPs remain billable
- Billing continues until the Public IP is deleted
Always remove unused Public IPs to avoid unnecessary charges.
Best Practices
Recommended usage:
- Use Public IPs only when internet access is required
- Prefer private IP communication within a VPC
- Review retained Public IPs regularly
- Delete unused Public IPs to stay within project limits
Summary
- Public IPs are standalone networking resources
- They can be attached to multiple service types
- Not all Public IPs are tied to VMs
- Default limit is 5 Public IPs per project
- Retained IPs remain visible, billable, and reusable
- Public IP lifecycle is independent from VM lifecycle