Cloud DB for MongoDB scenario
    • PDF

    Cloud DB for MongoDB scenario

    • PDF

    Article Summary

    Available in VPC

    NAVER Cloud Platform's Cloud DB for MongoDB easily and quickly builds MongoDB servers in cloud environments, and operates and manages them to enable stable cache service. The full sequence for utilizing NAVER Cloud Platform's Cloud DB for MongoDB is as follows.

    clouddbforpostgresql-procedure_01_vpc_en

    The descriptions for each step are as follows.

    1. Create application server
    2. Set access environment
    3. Test application server connection
    4. Create MongoDB Server
    5. Set ACG
    6. Test MongoDB server connection

    1. Create application server

    First, create an application server (app server) that will communicate with the MongoDB server to be created from the Cloud DB for MongoDB of the NAVER Cloud Platform console. Currently, Cloud DB for MongoDB is only accessible within NAVER Cloud Platform. Thus, the application server must also reside in NAVER Cloud Platform. The application server (app server) can be created from the Services > Compute > Server menu of the NAVER Cloud Platform console.
    You can refer to the following guides:

    2. Set access environment

    Once you've completed creating an application server, set up an access environment so that users can access the application server. You have two ways of setting the access environment, which are described as follows:

    • Set up access to a private domain using the public IP of NAVER Cloud Platform
    • Set up external access using the SSL VPN of NAVER Cloud Platform

    For access settings using the public IP, you need to check the admin (root) password required for the server access, using the Get admin password feature. For access settings using the SSL VPN, you can access the MongoDB server by installing the SSL VPN client on your personal PC. It is advantageous for security to use the SSL VPN to use it for administrative purposes.
    You can refer to the following guides:

    3. Test application server connection

    Once you complete setting up the access environment, use the terminal program to test if you can connect to the application server properly.
    You can refer to the following guides:

    4. Create MongoDB server

    After you complete testing the application server connection, create a MongoDB server that will communicate with the application server. The MongoDB server can be created from the Services > Database > Cloud DB for MongoDB menu of the NAVER Cloud Platform console without a separate service subscription request.
    You can refer to the following guides:

    Server redundancy configuration

    To prevent data loss and minimize service impact if failures occur, you can set server redundancy. Cloud DB for MongoDB creates a primary DB server and a secondary DB server. It provides a feature that automatically fails over to the secondary when the primary fails. According to the internal algorithm of MongoDB, a new primary server is selected among secondary servers.

    clouddbformongodb-procedure-failover_vpc_ko

    To configure server redundancy, select the cluster type as Single Replica Set or Sharding when creating the MongoDB server.

    Manage monitoring and event

    For MongoDB servers that have been created and are in operation, you can check monitoring for server performance and operating system status as well as events that occurred, and manage them for stable database service from the NAVER Cloud Platform console. You can also utilize the NAVER Cloud Platform's Cloud Insight for event and notification settings.

    Caution

    Additional charges apply when you request subscription to Cloud Insight. For the introduction on Cloud Insight and details about its pricing plans, refer to the Service > Management & Governance > Cloud Insight menu in the NAVER Cloud Platform portal.

    You can refer to the following guides:

    Manage management and administration permissions

    You can create sub accounts in addition to the main user account, and set various management and administration permissions for Cloud DB for MongoDB. You can design permissions by utilizing the System Managed and User Created policies in the NAVER Cloud Platform's Sub Account.

    Note

    The Sub Account is provided free of charge upon subscription request. For an introduction on Sub Account and more details about pricing plans, refer to the Service > Management & Governance > Sub Account menu in the NAVER Cloud Platform portal.

    You can refer to the following guides:

    Store log and backup files

    You can safely store the log files and backup files created from MongoDB servers using the NAVER Cloud Platform's Object Storage.

    Caution

    Additional fees apply when you request subscription to Object Storage. For the introduction on Object Storage and details about its pricing plans, refer to the Service > Storage > Object Storage menu in the NAVER Cloud Platform portal.

    You can refer to the following guides:

    5. Set ACG

    Set the ACG (Access Control Group) for the MongoDB server to allow the access of the application server to the created MongoDB server.
    You can refer to the following guides:

    6. Test MongoDB server connection

    Use the MongoDB Compass and test to see if you can properly connect to the created MongoDB server.
    You can refer to the following guides:


    Was this article helpful?

    Changing your password will log you out immediately. Use the new password to log back in.
    First name must have atleast 2 characters. Numbers and special characters are not allowed.
    Last name must have atleast 1 characters. Numbers and special characters are not allowed.
    Enter a valid email
    Enter a valid password
    Your profile has been successfully updated.