Skip to content

Commit 8c6036b

Browse files
committed
feat(OPS): update
1 parent 8dc2a0a commit 8c6036b

File tree

3 files changed

+44
-7
lines changed

3 files changed

+44
-7
lines changed
Lines changed: 30 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,34 @@
11
---
22
title: How to create a Cloud Essentials for OpenSearch deployment
33
description: This page provides a guide on how to set up a Cloud Essentials for OpenSearch deployment using the Scaleway console.
4-
tags:
4+
tags: opensearch search db engine data manage create deploy dashboard api
55
dates:
6-
validation:
7-
posted:
8-
categories:
9-
-
10-
---
6+
validation: 2025-07-29
7+
posted: 2025-07-29
8+
---
9+
10+
import Requirements from '@macros/iam/requirements.mdx'
11+
12+
This page explains how to create an OpenSearch deployment using the Scaleway console.
13+
14+
<Requirements />
15+
16+
- A Scaleway account logged into the [console](https://console.scaleway.com)
17+
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
18+
19+
## How to create a Cloud Essentials for OpenSearch deployment
20+
21+
1. Click **OpenSearch** in the **Databases** section of the console. The Cloud Essentials for OpenSearch dashboard displays.
22+
23+
2. Click **+ Create deployment**. A creation form displays.
24+
25+
3. Select an OpenSearch version for your deployment.
26+
27+
4. Select a region where your resource will be deployed.
28+
29+
5. Select a deployment configuration. You can choose between:
30+
31+
- **High Availability**: ensures fault tolerance in case of node failure, workload distribution across all nodes for improved performance, service continuity during rolling updates.
32+
- **Standalone**: cost-optimized single-node deployment for testing environments and non-critical, small-scale applications, without redundancy.
33+
34+
6. Choose a node type for your deployment. Refer to the [dedicated documentation](/opensearch/reference-content/shared-vs-dedicated-resources/) for more information on shared and dedicated compute resources.

pages/opensearch/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Dive into Scaleway Cloud Essentials for OpenSearch with our quickst
55

66
<ProductHeader
77
productName="Cloud Essentials for OpenSearch"
8-
openSearch="openSearch"
8+
productLogo="openSearch"
99
description="Cloud Essentials for OpenSearch is designed to help users in their reporting and data analysis tasks for business intelligence."
1010
url="/opensearch/quickstart"
1111
label=" Cloud Essentials for OpenSearch Quickstart"
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: Choosing between shared and dedicated resources
3+
description: This page provides information on the shared and dedicated node options available for Cloud Essentials for OpenSearch deployments.
4+
tags: opensearch search db engine node type shared dedicated compute resource
5+
dates:
6+
validation: 2025-07-29
7+
posted: 2025-07-29
8+
---
9+
10+
When creating a Cloud Essentials for OpenSearch deployment, selecting the appropriate node type is crucial for optimizing performance and cost. Two types of CPU provisioning are available: **shared** and **dedicated** vCPUs.
11+
12+
Understanding the difference between these two techniques is key to create a deployment adapted to your needs.
13+

0 commit comments

Comments
 (0)