---
title: "VPC server connection environment configuration"
slug: "server-ts-access-architecture-vpc"
tags: ["Server", "VPC", "Troubleshooting"]
updated: 2026-09-17T09:17:55Z
published: 2026-09-17T09:17:55Z
canonical: "guide.ncloud-docs.com/server-ts-access-architecture-vpc"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# VPC server connection environment configuration

Available in VPC

This document describes how to configure the VPC server connection environment for each subnet.

## VPC server connection environment configuration

Unlike Classic, in a VPC server, you cannot connect through port forwarding. The following shows how to configure a general server connection environment in VPC.

| Subnet type | How to access |
| --- | --- |
| Public Subnet | [Access through public IP](/docs/en/server-ts-access-architecture-vpc#PublicSubnet에생성한서버) |
| Private Subnet | [Bastion Host configuration](/docs/en/server-ts-access-architecture-vpc#BastionHost구성) |
| [IPSec VPN configuration](/docs/en/server-ts-access-architecture-vpc#IPsecVPN구성) |
| [SSL VPN configuration](/docs/en/server-ts-access-architecture-vpc#SSLVPN구성) |
| [Cloud Connect configuration](/docs/en/server-ts-access-architecture-vpc#CloudConnect구성) |

### Server created in a public subnet

For servers created in a public subnet, you can allocate a public IP for public communication. You can access the server with a public IP from outside through the public IP. The following shows how to access the server through the issued public IP.

1. Request a public IP.
  - See [Request public IP](/docs/en/server-publicip-vpc#%EA%B3%B5%EC%9D%B8IP%EC%8B%A0%EC%B2%AD)
2. Add the Source IP and the port needed for accessing the ACG of the server with the public IP allocated.
  - See [Set ACG](/docs/en/server-acg-vpc#ACG%EC%84%A4%EC%A0%95)
3. Access the server through the public IP.
  - See [Access server](/docs/en/server-access-vpc)

### Server created in a private subnet

You can access the server created in a private subnet using the following methods:

- [Bastion Host configuration](/docs/en/server-ts-access-architecture-vpc#BastionHost%EA%B5%AC%EC%84%B1)
- [IPsec VPN configuration](/docs/en/server-ts-access-architecture-vpc#IPsecVPN%EA%B5%AC%EC%84%B1)
- [Cloud Connect configuration](/docs/en/server-ts-access-architecture-vpc#CloudConnect%EA%B5%AC%EC%84%B1)
- [SSL VPN configuration](/docs/en/server-ts-access-architecture-vpc#SSLVPN%EA%B5%AC%EC%84%B1)

          Note

          

For more information on how to use VPC and create subnets, see the following guides:

- [Create VPC](/docs/en/vpc-manage-vpc#VPC%EC%83%9D%EC%84%B1)
- [Create subnet](/docs/en/vpc-subnetmanage-vpc#Subnet%EC%83%9D%EC%84%B1)
- [VPC scenarios](/docs/en/vpc-procedure-vpc)

#### Bastion Host configuration

Bastion Host is a private access server configured in the public subnet. By configuring and operating Bastion Host, you can easily access the private subnet. You can use various features such as access record logging and authentication key settings by setting the operating system. ![vpc-access-bastion](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/compute-vpc-server-access-architecture-vpc-access-bastion.png?sv=2026-02-06&spr=https&st=2026-11-14T05%3A16%3A29Z&se=2026-11-14T06%3A16%3A29Z&sr=c&sp=r&sig=iZ7D2f4j%2BFzmtjlIVsEB1v0vUFnk38wRO2a1Tv%2F%2Fq2c%3D)

The following describes how to configure a Bastion Host.

1. Configure the public subnet and private subnet.
2. Create a server in the public subnet for the Bastion Host.
3. Allocate a public IP to the Bastion Host and check the admin password of the Bastion Host server.
4. Add the Source IP for accessing the ACG of Bastion Host and the port needed for access.
  - See [ACG](/docs/en/server-acg-vpc)
5. Access the allocated public IP through SSH (Linux)/RDP (Windows) or other means.
  - See [Access server](/docs/en/server-access-vpc)
6. Re-connect to the address of the destination server (private subnet) in the server accessed through SSH (Linux)/RDP (Windows).
  - Here, you must check the admin password of the server to access in advance as well.

#### IPsec VPN configuration

You can connect a customer private network to the VPC network through IPsec VPN. When configuring IPsec VPN, you can access not only private subnets, but also servers configured in a public subnet through a private IP. ![compute-vpc-server-access-architecture-vpc-access-ipsec_en](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/compute-vpc-server-access-architecture-vpc-access-ipsec_en.png?sv=2026-02-06&spr=https&st=2026-11-14T05%3A16%3A29Z&se=2026-11-14T06%3A16%3A29Z&sr=c&sp=r&sig=iZ7D2f4j%2BFzmtjlIVsEB1v0vUFnk38wRO2a1Tv%2F%2Fq2c%3D)

The following describes how to configure an IPsec VPN.

1. Configure the VPC environment.
2. Configure a VGW.
  - See [Virtual Private Gateway (new)](/docs/en/virtual-private-gateway-new)
3. Configure the IPsec VPN.
4. Add the Source IP for accessing the ACG of the server to access and the port needed for access.
  - See [ACG](/docs/en/server-acg-vpc)
5. Access the server of NAVER Cloud Platform on a terminal such as a PC or server of the customer private network.
  - See [Access server](/docs/en/server-access-vpc)

          Note

          

For more information, see the [IPsec VPN user guide](/docs/en/ipsecvpn-overview) of VPC environment.

#### SSL VPN configuration

If you cannot configure IPsec VPN in a remote place, you can access the server through SSL VPN. SSL VPN provides a client that can directly access the VPC network through encrypted communication from the PC. When configuring SSL VPN, you can access not only private subnets, but also servers configured in a public subnet through a private IP. ![compute-vpc-server-access-architecture-vpc-access-sslvpn_en](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/compute-vpc-server-access-architecture-vpc-access-sslvpn_en.png?sv=2026-02-06&spr=https&st=2026-11-14T05%3A16%3A29Z&se=2026-11-14T06%3A16%3A29Z&sr=c&sp=r&sig=iZ7D2f4j%2BFzmtjlIVsEB1v0vUFnk38wRO2a1Tv%2F%2Fq2c%3D)

The following describes how to configure an SSL VPN.

1. Configure the VPC environment.
2. Configure the SSL VPN.
3. Add the Source IP for accessing the ACG of the server to access and the port needed for access.
  - See [ACG](/docs/en/server-acg-vpc)
4. Access the server of NAVER Cloud Platform through the SSL VPN Client of the customer private network PC.
  - See [Access server](/docs/en/server-access-vpc)

          Note

          

For more information, see the [SSL VPN user guide](/docs/en/sslvpn-overview) of VPC environment.

#### Cloud Connect configuration

Cloud Connect refers to the point of contact where a dedicated external line comes into NAVER Cloud Platform. The method to complete Cloud Connect and access the server is the same as in [IPsec VPN](/docs/en/server-ts-access-architecture-vpc#IPsecVPN%EA%B5%AC%EC%84%B1). ![compute-vpc-server-access-architecture-vpc-access-cc_en](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/compute-vpc-server-access-architecture-vpc-access-cc_en.png?sv=2026-02-06&spr=https&st=2026-11-14T05%3A16%3A29Z&se=2026-11-14T06%3A16%3A29Z&sr=c&sp=r&sig=iZ7D2f4j%2BFzmtjlIVsEB1v0vUFnk38wRO2a1Tv%2F%2Fq2c%3D)

The following describes how to configure Cloud Connect.

1. Configure the VPC environment.
2. Configure a VGW.
  - See [Virtual Private Gateway (new)](/docs/en/virtual-private-gateway-new)
3. Complete the configuration of Cloud Connect.
4. Add the Source IP for accessing the ACG of the server to access and the port needed for access.
  - See [ACG](/docs/en/server-acg-vpc)
5. Access the server of NAVER Cloud Platform on a terminal such as a PC or server of the customer private network.
  - See [Access server](/docs/en/server-access-vpc)

          Note

          

For more information, see the [Cloud Connect user guide](/docs/en/cloudconnect-vpc) of VPC environment.