Use environment summary
You can view the use environment provided by NAVER Cloud Platform before use.
The NAVER Cloud Platform use environment refers to the base on which you can use services provided by NAVER Cloud Platform. Region, zone, and platform are all elements of a use environment. The services that are provided differ, depending on these elements. Make sure to check the use environment of the service you want before using NAVER Cloud Platform.
Region refers to clusters of infrastructures of one or more zones built on key locations for effective service. Each region is sectioned by the geological location of the servers that provide services. The closer a user is to a region, the faster its servers respond. Choose your region in consideration of the physical distance between you and the region.
NAVER Cloud Platform is available for the Korea, U.S. West, Hong Kong, Singapore, Japan, and Germany regions.
Each region may vary in the services they offer, except for services that are common in all regions such as ACG, Init-Script, Monitoring, Global DNS, Sub Account, etc. Before requesting subscription to any service, check the services provided by the use environment.
The following services are unavailable in global regions outside of Singapore, Japan, U.S., and Germany until region rebuilding is completed: SSD Server, GPU Server, Auto Scaling, Object Storage, and NAS.
- Object Storage: A service that communicates publicly through APIs. There may be internet line latency issues.
- NAS: Uses a private network through the dedicated global line, so there may be dedicated line latency issues.
My server images and snapshots can be moved and cloned to other regions for use.
- NAVER Cloud's dedicated global line network is used when moving to a different region.
- Existing server images and snapshots can't be deleted while they are being moved to another region for stable replication.
The zone refers to networks and data centers that physically exist and are separated in each country-specific region. Each zone exists independently, so a failure occurring in a specific zone won't affect other zones.
There are two types of zones: single zone where one region contains one zone, and multi-zone where one region contains multiple zones. NAVER Cloud Platform offers multi-zone in Korea and Singapore regions, whereas single-zone in other global regions. Multi-zone will continue to expand.
You can set up server redundancy and build a Disaster Recovery (DR) system for your service's availability and continuity.
High availability (HA) is a service that is provided to prepare for failures from the physical server, such as those involving memory, CPU, and power supply.
HA is a service for preventing hardware failures from expanding into the virtual machine (VM) servers. It supports live migration, which automatically migrates the VM on the host server to another secure host server when a failure occurs in the first host server. However, the VM server is rebooted when an error occurs and live migration can't be initiated.
If the service is being operated with a single VM server, then it is recommended that you also set up redundancy for VM servers in order to reduce the frequency of failures that may occur as a result of rebooting the VM server.
The Operation of DR (Disaster Recovery) system is a system that recovers servers that have been shut down due to various disasters and threats back to their normal running state in a short period of time.
DR differentiates between the main zone and DR zone, and regularly backs up data in the main zone to the DR zone. In case the service faces problems due to natural disasters or computer accidents, it recovers data safely from the DR zone and enables the service to be continued. NAVER Cloud Platform's Korea region is multi-zone, where physically separated servers can perform the roles of the main zone and DR zone, mutually complementing each other.
We advise you to build a DR system so that you can operate services without stops, even in disaster situations.
DR systems can only be built in a region where multi-zone is supported.
The platform refers to an element that separates environments with different impact range for each service. NAVER Cloud Platform provides a VPC environment and a Classic environment, and each environment operates independently and there may be slight differences in the services provided. For instance, Compute services in the Classic environment can't be used in the VPC environment. Compute services for VPC can't be used in the Classic environment, either. In addition, Networking services(Load Balancer, IPsec VPN, etc.) in the Classic environment can't be used in the VPC environment. However, sending and linking data between the environments via public IP network are available.
Make sure to check the use environment of the service you want before using NAVER Cloud Platform.
|- Establish resources on a Shared Network
- Access between tenants is controlled by the Access Control Group (ACG)
- Establish workloads based on private IPs assigned by CSP
|- Virtual Private Cloud (VPC), a private network only for the client, is provided on public cloud
- User-designed network and user-assigned private IP
- Each VPC is logically completely isolated
- Available to implement in a similar way as the client's existing data center network
- Up to 3 can be created per client account and region
|Management, AI, and Security services except IaaS can be used regardless of the platform type|