Architecture design
Account, network and identity structure (landing zone) with multi-zone redundancy as the default.
- VPC · Subnet · NAT Gateway
- Sub Account (IAM)
- Load Balancer · Global DNS
- Ncloud Kubernetes Service
Cloud MSP · NAVER Cloud
NAVER Cloud operations and Cloud DB, together
From standard VPC and Sub Account design to Cloud DB for MySQL and PostgreSQL tuning, operated for the Korean cloud environment.
Reference architecture
Reference architecture on NAVER Cloud
Boundaries set with public/private VPC subnets and ACGs; Cloud DB runs with HA and automated backups by default.
Sub AccountMFA · least privilege
VPCpublic / private subnet
Identity & network boundary
Load BalancerACG
Server · NKSKR-1 / KR-2 zones
Application → data tier
Cloud DBMySQL · PostgreSQL HA
Read replicaread scale
Backupautomated backup · Object Storage
Cloud Insight · Security MonitoringCloud AdvisorTerraform (ncloud)
- Console and API permissions separated with Sub Account and MFA
- Cloud DB in private subnets with minimal ACG openings
- Alerting on Cloud Insight metrics and events
- Where the public-sector (Gov) environment is required, confirm the available services in advance
MSP scope
MSP scope on NAVER Cloud
Representative services we use in each area, adjusted to your environment and contract scope.
Migration to cloud
Step-by-step moves, from server rehosting to managed database replatforming.
- Database Migration Service
- Object Migration
- Migration Management
- Server image · rsync-based rehost
24x7 monitoring & operations
Metrics, logs and events collected and run through incident and change processes.
- Cloud Insight
- Cloud Log Analytics
- Cloud Activity Tracer
- Auto Scaling
Cost optimization (FinOps)
Visibility, budget alerts, right-sizing and commitment reviews on a recurring cycle.
- Billing & cost reports (console)
- Cloud Advisor
- Server spec right-sizing
- Scheduled stop / start
Security & compliance
Least privilege, encryption, audit logging and security-recommendation reviews by default.
- Sub Account · MFA
- Security Monitoring
- Key Management Service
- ACG · Network ACL
Backup & DR
Backup policies and recovery objectives (RPO/RTO), proven by restore drills.
- Backup
- Object Storage · Archive Storage
- Cloud DB automated backup
- Cross-zone redundancy
Managed database operations
DBA-level care for parameters, performance and the version lifecycle of managed databases.
- Cloud DB for MySQL
- Cloud DB for PostgreSQL
- Cloud DB for MSSQL · MongoDB · Cache
- MariaDB server image (self-managed)
IaC & automation
Infrastructure as code, with deployments and routine checks automated in pipelines.
- Terraform (ncloud provider)
- Ncloud CLI · API
- SourceCommit · SourcePipeline
- Ansible
Managed databases
Choosing a managed database on NAVER Cloud
For each open-source engine: the managed service available on this cloud, or the self-managed alternative.
| Engine | Managed service / alternative | Notes |
|---|---|---|
| MySQL | Cloud DB for MySQL | Managed service available — we manage parameters, performance and upgrade plans |
| PostgreSQL | Cloud DB for PostgreSQL | Managed service available — we manage parameters, performance and upgrade plans |
| MariaDB | MariaDB server image / Marketplace (self-managed) | No managed service — self-managed on VMs/containers (linked to our open-source DB services) |
| InfluxDB | Server (self-managed) | No managed service — self-managed on VMs/containers (linked to our open-source DB services) |
| Oracle · SQL Server | Cloud DB for MSSQL / Server; → MySQL · PostgreSQL | Usually the source of a heterogeneous migration — see Data Migration |
NAVER Cloud has no managed Cloud DB product for MariaDB (per official docs, October 2026). MariaDB is self-managed from a server image or Marketplace, or moved to Cloud DB for MySQL.
Migration to cloud
Migrating to NAVER Cloud
Assess
Inventory servers and databases, map dependencies, baseline performance, review licensing and choose rehost, replatform or refactor.
Landing zone
Build account, network, identity and logging standards first, as code.
Migrate
We start from Server image · rsync / OS-level replication for servers and NCP Database Migration Service · native replication for databases, with ora2pg · pgloader · mydumper for schema conversion.
Validate & cut over
Verify data consistency and performance, switch over against agreed criteria and keep a rollback path.
Stabilize & optimize
Heightened monitoring during hypercare, then cost and performance optimization as routine operations.
Security & compliance
Korean regulatory & security considerations
- Region: NAVER Cloud KR region (KR-1 · KR-2 zones) — document where data and backup copies are stored
- Access control, encryption and access-log retention designed with the Personal Information Protection Act and ISMS-P in mind
- Public sector: confirm whether CSAP (Cloud Security Assurance Program) applies and which certification scope is required
- Operating procedures that keep audit logs, change history and access reviews as evidence
These are general considerations. OpenDB Works does not act as a certification agent or guarantee certification; interpretation of requirements rests with your security team and the certification body.
FAQ
Frequently asked questions
Cloud DB for PostgreSQL or self-managed?
We weigh extension and parameter freedom against operating effort. If you need extensions the managed service does not support, we recommend a self-managed server.
Do you work on public-sector projects?
We confirm which services and CSAP certification scope the public-sector environment offers against the project requirements before designing. Eligibility is judged by the contracting agency.
Are you a NAVER Cloud partner?
We do not publish partner status on this site; we can share it during consultation if relevant.
Shall we start by reviewing your cloud and databases as they are today?
Tell us your clouds, database versions, topology and concerns, and we will propose an assessment scope and approach.