Load Balancer specifications
- Print
- PDF
Load Balancer specifications
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
The latest service changes have not yet been reflected in this content. We will update the content as soon as possible. Please refer to the Korean version for information on the latest updates.
Available in Classic and VPC
Check the cloud environment specifications, restrictions, and pricing for the smooth use of Load Balancer.
Cloud environment specifications
The following are cloud environment specifications supported by Load Balancer.
| Item | Supported specifications |
|---|---|
| Regions | Korea, US West, Hong Kong, Singapore, Japan, and Germany |
| Classic | Supported regions: Korea, US West, Hong Kong, Singapore, Japan, and Germany |
| VPC | Supported regions: Korea, Japan, and Singapore |
| Languages | Korean, English, and Japanese |
Restrictions
The following are restrictions when using the Load Balancer service.
- VPC environment
- Up to 50 servers can be bound.
- In Neuro Cloud, only Private Load Balancer is available.
- In Classic
- One server can be bound to multiple load balancers, but multi-binding by port is not supported.
- The 22, 3389, 18080~18095, 64000, 65130, and 65131 ports cannot be used as the Load Balancer port since they reserved for Load Balancer management.
- Up to 50 servers can be bound.
Usage fee
Load Balancer has differentiated billing standards by use environment. Basic fee for own possession and fee for network traffic sent by the load balancer are billed. For details on Load Balancer pricing, see the Service > Networking > Load Balancer menu on the portal or the pricing by region guide page.
Was this article helpful?