- Print
- PDF
Cloud Search overview
- Print
- PDF
Available in Classic and VPC
Cloud Search is a managed service of NAVER Cloud Platform that allows you to easily set up and manage the search function of your website. You can build a search service with minimal cost and time by implementing a search function with many complex requirements on a cloud basis without building a separate infrastructure or platform.
Various features provided by Cloud Search
The following describes the various features offered by Cloud Search.
- Implementation of simple search service: provides a fully managed search engine service to easily implement a search environment in the web console of NAVER Cloud Platform
- Rich options for indexing configuration: rich options for indexing configuration to accommodate a variety of search-related needs
- Korean morpheme analysis: morphological analysis processing of the Korean language with NAVER's know-how
- Processing for multiple languages, stopwords, and synonyms: processing features for multiple languages such as Korean, English, Japanese, Chinese (simplified and traditional), Indonesian, and Thai, as well as stopwords and synonyms
- Monitoring: through monitoring tools, resize the container as needed by monitoring several indicators
- Search query analysis: can search popular search terms of imported search queries and statistics by time/region
About Cloud Search guide
Cloud Search provides its services in the Korea Region. See the following table of contents and their details for best use of Cloud Search.
- Cloud Search overview: introduction to Cloud Search, related supporting resources for use, and FAQ guide
- Prerequisites for using Cloud Search: guide to support specifications for using Cloud Search
- Cloud Search scenario: guide on the entire process for using Cloud Search
- Get started: guide on how to start using Cloud Search
- Subscribe and unsubscribe: information on how to subscribe to and unsubscribe from Cloud Search on the NAVER Cloud Platform console
- Using Cloud Search: guide on how to use Cloud Search
- Domain: how to create and manage domains and set up search engines
- Domain screen: how to configure the domain screen and check the domain list
- Creating domain: guide on how to create a domain
- Editing and deleting domains: guide on how to edit domain information and delete domains
- Sections and indexes settings: guide on how to set sections and indexes, index setting items
- Test search and search settings: guide on how to set up search engines, such as search test methods and ranking modules, auto-completion, stopwords, thesaurus, and so on
- Managing domain: guide on how to upload and manage documents, change the container type and number of domains, and limit usage
- Monitoring: information on how to check service usage by domain
- Query analysis: information on how to check search term rankings by domain and search trend by region
- Search query: guide on the search query entered when requesting a search
- Ranking formulas: guide to creating and using ranking formulas to sort search results
- Domain: how to create and manage domains and set up search engines
- Cloud Search examples: download the example document provided by Cloud Search
- Managing Cloud Search permissions: how to manage Cloud Search permissions with Sub Accounts
- Cloud Search glossary: information on key terms you must know when using Cloud Search
- Cloud Search release notes: update history of Cloud Search user guide
Cloud Search related resources
The NAVER Cloud Platform provides various related resources as well as the guide to help customers better understand Cloud Search. If you're a developer or marketer in need of detailed information while you're considering adopting Cloud Search or establishing data related policies, please make good use of the following resources.
- Improvement in comprehension and usage methods for Cloud Search
- Cloud Search API guide: how to use API for Cloud Search developers
- Ncloud use environment guide: a usage guide on VPC and Classic environments and supported features
- Pricing plans, features, and detailed functions: summary of pricing plans, features, and detailed functions of Cloud Search
- FAQ: frequently asked questions from Cloud Search users
- Latest service news: latest news related to Cloud Search
- Contact us: send direct inquiries in case of any unresolved questions that were not answered by the guide
- Building a search service with Cloud Search: Cloud Search easy start guide
- Guides for services integrated to Cloud Search
- Sub Account guide: how to use Sub Account, which helps to manage Cloud Search’s administration permissions
Check FAQs first.
You can get your questions answered quickly by referring to the answers in the FAQ before reading the guides. If your questions are not resolved in the FAQ, see the guides to find the information you want.
Q. What is Cloud Search?
A. Cloud Search is a cloud-based development platform that facilitates easy implementation of the search features required by user's website. You can easily create a search engine without building a separate infrastructure using Cloud Search.
Q. How can I use Cloud Search?
A. You can manage domains through console and API and use search services through API. For more details, see Cloud Search scenarios.
Q. When can I use Cloud Search?
A. You can use it whenever you need to search.
- If you are running a shopping mall, you can use it for product searches.
- In the case of a company, you can use it for searching internal information such as employee information, notices, and posts.
- In case of providing a bulletin board service, you can use it to implement a bulletin board search function.
Q. What are the advantages of Cloud Search?
A. The advantages of Cloud Search are as follows.
- You can create a search engine with just a few clicks without building a separate infrastructure.
- It does not require separate server operation or package installation.
- Thanks to Docker technology, you can easily expand it as needed.
- Even if a server fails, it is possible to automatically restore and configure redundancy.
- You can use it easily without having to understand the difficult technology of search engines.
- With its technology accumulated over the past 20 years, NAVER search engine has achieved a superior level of morpheme analysis in Korean and search response speed in comparison to other search engines.
- Using only the necessary infrastructure and immediately turning away any unnecessary resources allow you to minimize operational costs.
Q. Why should I use Cloud Search?
A. If you use Cloud Search, you can easily solve the difficult and time-consuming task of developing a search service.
Required work to develop a search service | Resolved using Cloud Search |
---|---|
Discuss creation of search service with planners and developers | Planners can create and test their own domains |
Discuss ranking methods with ranking engineers | Edit ranking method and apply service in real time |
Install engine and various packages on physical server equipment | |
Document index settings and document input integration | Use the provided document input and integrated system |
Implement search logic | Use common search logic provided |
Respond to failure and error | Can respond to server operation and failure without a separate operating organization |
Q. What is database connectivity?
A. This is a function that allows you to create a Cloud Search domain using the data in the NAVER Cloud Platform server or DB server created with Cloud DB, or convert data into a document and upload it. We support the following databases:
- When connecting to a DB server in a VPC environment with the same account in a VPC environment: MySQL, MariaDB, MSSQL, MongoDB
- When connecting through the host and public IP of the DB server: MySQL, MariaDB
Q. What procedure is required to create and connect a database with the server image of Server?
A. After performing the following steps, connect with the database to create a domain or upload a document from the database.
- Create a server by selecting the image type DBMS. (see Creating server (VPC, Classic))
- Request a public IP and apply it to the created server. (see Public IP (VPC, Classic))
- Add the Cloud Search connection IP and the connection port of the configured DB server to the ACG applied to the server. (see ACG (VPC, Classic))
- Cloud Search connection IP
- In a VPC environment, when connecting to a DB server in a VPC environment owned by the same account: 169.254.83.16, 169.254.83.17
- When connecting through DB server's host and public IP: 115.85.176.%
- Cloud Search connection IP
- Add a user who allows access to the Cloud Search connection IP to the DB server.
Q. What procedures are required to connect to a database in Cloud DB for MySQL?
A. After performing the following steps, connect with the database to create a domain or upload a document from the database.
- Create a DB server in Cloud DB for MySQL. (see DB Server)
- Set the public domain on the DB server. (see Managing Public domain)
- Add the Cloud Search connection IP and the connection port of the configured DB server to the ACG applied to the DB server. (see ACG (VPC, Classic))
- Cloud Search connection IP
- In a VPC environment, when connecting to a DB server in a VPC environment owned by the same account: 169.254.83.16, 169.254.83.17
- When connecting through DB server's host and public IP: 115.85.176.%
- Cloud Search connection IP
- Add a user who allows access to the Cloud Search connection IP to the DB server. (see Managing DB user)
For more information about Cloud DB for MySQL, see Cloud DB for MySQL Guide.
Q. What is the process of uploading DB data?
A. Uploading DB data proceeds in the following order.
- When requesting to upload DB data, it will query the data from the server with the entered information.
- It receives data from the DB server and converts it into a Cloud Search document (JSON).
- It converts documents in chunk units so that the document data is less than 100 MB.
- Converted documents are sequentially uploaded to Cloud Search and indexed.
- When indexing is complete, you can check the upload result through the console notification.