Learn the core architecture and DevOps of NAVER Cloud Platform (NCP). Covers container design on NKS (Ncloud Kubernetes Service), VPC virtual networks and ACG firewall rules, IAM account management with Sub Accounts, and integration with the NCP CLI and Terraform.
Intermediate
Updated Oct 1, 2026
~3 min read
7 sections
4 code examples
☁️
Operating Kubernetes on NKSVPC & ACG security designAccess control with Sub AccountsNCP CLI commands
Learn the core architecture and DevOps of NAVER Cloud Platform (NCP). Covers container design on NKS (Ncloud Kubernetes Service), VPC virtual networks and ACG firewall rules, IAM account management with Sub Accounts, and integration with the NCP CLI and Terraform. Rather than listing concepts, this guide is organized so you can follow the content in the order you have to make decisions on a real project.
Key perspective
Infrastructure / operations
Rather than memorizing install commands, understand the order in which traffic, runtime, observability, and incident response connect.
Operating Kubernetes on NKSVPC & ACG security designAccess control with Sub AccountsNCP CLI commands
Architecture diagrams
To make what you read stick, it helps to capture the flow as a picture first. The two diagrams below are reference maps you can keep coming back to while learning NCP.
Learning flow
Rendering diagram…
Architecture view
Rendering diagram…
Operating Kubernetes on NKS
When you first open NCP, the big picture matters more than individual commands. This section starts with the problems the concepts ahead were created to solve.
NKS (Ncloud Kubernetes Service) makes it easy to build Kubernetes clusters in the NAVER Cloud environment. Node pools are added/shrunk easily through the cluster management console or API, and images are pulled through secure integration with Ncloud Container Registry (NCR).
BASH
# Fetch the Kubernetes configuration from the NKS console or CLI# (NCP manages this through downloading the credentials file and configuring ncloud-cli.)kubectl get nodes -o wide
VPC & ACG network security
Here you look at VPC & ACG network security alongside real code. Rather than copying the example as-is, read it with an eye on the inputs, the outputs, and the parts most likely to change.
In an NCP VPC environment, virtual servers (Server) and DB instances are isolated in private subnets, and ACG (Access Control Group) rules are defined to block access. For outbound internet connectivity, design the route tables to go through a public IP and NAT Gateway.
Example ACG rulesTEXT
[Inbound rules]
Protocol | Source | Ports | Description
TCP | 0.0.0.0/0 | 80, 443 | Public web service ports
TCP | 203.0.113.10 | 22 | SSH allowed from a specific admin IP
[Outbound rules]
Protocol | Destination | Ports | Description
TCP | 0.0.0.0/0 | 1-65535 | External package updates and API calls
Sub Account security
This section covers Sub Account security from a practical perspective. Instead of memorizing the concept, focus on the situations in which you would reach for it.
Exposure of the API key of the NAVER Cloud main (Root) account is a very serious risk. Use the Sub Account feature to create secondary accounts per job function, grant role-based policies (Ncloud Kubernetes Service administrator, Server administrator, and so on), and use individual API authentication keys.
NCP CLI & Terraform
Here you look at NCP CLI & Terraform alongside real code. Rather than copying the example as-is, read it with an eye on the inputs, the outputs, and the parts most likely to change.
ncloud-cli is the official CLI for viewing and creating NCP resources such as servers, VPCs, and NKS from the shell without opening the console. Rather than running repeated infrastructure setup one command at a time in the CLI, manage it as declarative code with the Terraform NCP Provider, and you can track the history of resource changes in Git and review them with teammates.
BASH
# Configure ncloud-cli (register the API authentication keys)ncloud configure# List server instancesncloud server getServerInstanceList# List NKS clustersncloud nks getClusterList
main.tfHCL
terraform { required_providers { ncloud = { source = "NaverCloudPlatform/ncloud" version = "~> 2.3" } }}provider "ncloud" { access_key = var.ncloud_access_key secret_key = var.ncloud_secret_key region = "KR" site = "public"}resource "ncloud_vpc" "main" { name = "vpc-terraform" ipv4_cidr_block = "10.0.0.0/16"}
NCP practical design
NCP practical design is a point where the options diverge. Using the table to compare what each approach is for and how it differs in operation makes later decisions much easier.
NCP design follows the principles of separating virtual networks by Zone and private subnet, controlling port ranges in ACG firewall rules, and keeping Sub Account permissions individually separate.
Decision point
Question to ask
Practical guideline
Boundaries
Which parts of the NCP code are most likely to change?
Separate input/output, configuration, external integrations, and the core rules.
State
Where is state created and where does it go away?
Make the owner and lifecycle of state visible in the code.
Failure
What does the caller receive on failure?
Decide the timeout, fallback, and error contract first.
NCP operating standards
This section covers NCP operating standards from a practical perspective. Instead of memorizing the concept, focus on the situations in which you would reach for it.
Monitor the Ncloud Monitoring metric dashboards, track misuse of Sub Account API keys, manage server disk capacity, and maintain the allowlist of ACG outbound ports.
NCP verification strategy
NCP verification strategy is a point where the options diverge. Using the table to compare what each approach is for and how it differs in operation makes later decisions much easier.
Run ACG inbound security audits, verification of NCP CLI call responses, tenant network reachability tests, and backup policy validity checks.
Quality axis
How to verify
Definition of done
Correctness
Automate the normal/failure cases.
The core scenarios pass reproducibly.
Regression prevention
When fixing a bug, leave the same case behind as a test.
The same failure is not deployed again.
Operability
Check the logs, metrics, and alerts.
There is a path for tracing the cause when a problem occurs.
NCP: frequently asked questions
When do teams choose Naver Cloud Platform?
It is often chosen when data has to stay in Korea, when certification requirements for the Korean public or financial sectors have to be met, and when Korean-language technical support and billing in Korean won are needed. Integration with Naver services such as AI and maps is also straightforward.
What changes for someone moving from AWS to NCP?
The basic building blocks, virtual servers, VPC, object storage, managed databases, and managed Kubernetes, all have counterparts, so the concepts carry over. Service names, the console layout, and the APIs differ, and the range of services is not the same, so check first that the features you need exist.
Can I use infrastructure-as-code tools such as Terraform with NCP?
Yes. A Terraform provider for NCP is available, so servers and networks can be defined and managed as code. Check the provider documentation for the range of supported resources.