Create Endpoint

Endpoint Creation Process

1. Log in to the VNG Cloud console at: https://hcm-3-vnetwork.console.vngcloud.vn/endpoint/list

   • Ensure that the selected region is HCM.

2. From the left-hand navigation panel, click on the “Endpoint” menu.

3. Click “Create an Endpoint” to begin the setup process.

4. Enter the required information for the Endpoint:

   • Endpoint Name: Provide a name for the new Endpoint.

   • Select Region/Zone: Choose the appropriate region and availability zone (e.g., HCM-1A, HCM-1B, etc.).

   • Select Service: Choose a VNG Cloud service to connect to from the supported list: vServer, vStorage, vMonitor, vCR, IAM.

   • Service Package: The Endpoint is provisioned with the default Standard package.

     • No manual selection is required.

5. Select the VPC and Subnet to connect to the VNG Cloud service via the service Endpoint.

6. Private DNS Configuration:

   • If the selected VPC supports DNS, the “Enable Private DNS” option will be available.

     • When enabled, domain names will automatically resolve to internal IPs — no manual host entries are required.

   • If the VPC does not support DNS, the option will be disabled by default.

     • In this case, users must manually configure host entries to access the service.

7. Review service pricing and configuration details in the “Summary” section.

8. Click “CREATE ENDPOINT” to proceed.

9. The system will begin provisioning the Endpoint.

   • Once creation is complete, the new Endpoint will appear in the Endpoint list view.

How to Use the Endpoint

For Endpoints Created in VPCs Without DNS Support

When the VPC does not support DNS, the "Enable Private DNS" option will be unavailable during Endpoint creation. As a result, DNS name resolution will not be applied automatically, and users will not be able to access the Endpoint Service directly after creation.

Manual Configuration Steps:

To configure private access from your server to the Endpoint Service, follow these steps:

1. Open the Endpoint Management Page

   • Navigate to the list of created Endpoints.

   • Select the Endpoint you wish to configure.

2. Identify Key Information On the Endpoint detail page, the system will display two important items:

   • Endpoint URL: The public domain name for accessing the service via the Endpoint.

   • Endpoint IP: The internal IP address assigned to the Endpoint.

3. Configure the Host File on Your Server On each server that needs to access the service, add a host entry:

   • For Linux/macOS: /etc/hosts

   • For Windows: C:\Windows\System32\drivers\etc\hosts

   Entry format:

   Copy

   <Endpoint IP>    <Endpoint URL>

   Example:

   Copy

   10.0.5.123    service.example.internal

4. Save changes and verify that domain name resolution points to the correct Endpoint IP.

✅ Note: Host entry configuration is only required on servers located within the same VPC or that have a valid network route to the Endpoint Service.

Add host entries on servers that need to access the service via the Endpoint Service.

Private Endpoints in a VPC with DNS Support

When using a Private Endpoint, customers can access VNG Cloud services through a private network instead of the public internet. If DNS support is enabled, service access becomes seamless and more convenient, thanks to the ability to override DNS A records.

DNS Mechanism with Private Endpoints

a. Unique Domain per Endpoint

When a Private Endpoint is created with DNS support enabled, the system assigns a unique domain name to the endpoint. This domain can be used to access the corresponding service directly via the private IP of the endpoint.

Example: Private domain for the vStorage HCM03 service:

https://enp-ccd7fa25-a617-4e87-a929-97a7c933c19c-vstorage-hcm03.vpce.vngcloud.vn

b. “Enable Private DNS” Option

When configuring a Private Endpoint, enabling the "Private DNS" option allows an alternative access method using the service's official domain.

In VPCs that support internal DNS resolution (DNS override), the A record of the service's domain will be overridden to point to the private IP of the endpoint instead of the public IP.

🔒 This ensures all traffic remains on the private network while keeping the domain name unchanged.

Important constraint: Each VPC is allowed to have only one endpoint with Private DNS enabled per service.

Example: Default domain for accessing vStorage HCM03 service:

https://hcm03.vstorage.vngcloud.vn

Supported Services and Default Domains