AWS OpenSearch
SleakOps integrates with Amazon OpenSearch (formerly known as Amazon Elasticsearch Service), a powerful search and analytics engine designed to help you search, analyze, and visualize data in real time. By leveraging OpenSearch in SleakOps, you can quickly deploy, manage, and scale your search infrastructure, gaining valuable insights from your data.
For more information on OpenSearch and its capabilities, you can refer to the Amazon OpenSearch Service Documentation .
What are the use cases for OpenSearch?
OpenSearch is commonly used for full-text search, real-time analytics, monitoring and observability, and log analysis. It is also ideal for powering search functionalities on websites and applications.
What does "Dedicated Master Enabled" mean?
When enabled, SleakOps sets up dedicated master nodes that help with managing the OpenSearch domain. They provide enhanced stability by separating management tasks from data nodes. This is highly recommended for production workloads.
What is the recommended configuration for master nodes in production?
For production environments, SleakOps recommends using 3 dedicated master nodes to improve the stability and performance of your OpenSearch cluster.
Set up your OpenSearch
1. Add AWS OpenSearch as a Dependency
To integrate OpenSearch with SleakOps:
- In the SleakOps console, go to the "Dependencies" section
- Choose "SQS" from the list of available dependency types. For more detail see Dependencies: Integrating Databases, Caching, and Messaging Services.
2. Set up your OpenSearch.
When adding OpenSearch as a dependency in SleakOps, you need to configure several key attributes:
| Attribute | Description |
|---|---|
| FIFO Queue | Specifies the type of SQS queue. Where Standard Queue (for most use cases) or FIFO Queue (if message ordering is required)` |
| FIFO Deduplication | Only for FIFO Queues, in order to avoid duplicates. |
| Message Retention Period | Specifies the amount of time a message will be retained in the queue if it hasn't been consumed. |
| Maximum Message Size | The maximum size of a message that can be sent to the SQS queue. |
| Delivery Delay in Seconds | The delay between the message being sent to SQS and it being visible in the queue. No delay by default. |
| Receive Message Wait Time | Determines how long a ReceiveMessage call waits if no messages are available in the queue. |
| Visibility Timeout | The duration that a message remains invisible after a receiving component reads it from the queue. |
| Dead-Letter Queue (DLQ) | Add a queue where messages that fail to be processed multiple times are sent for additional analysis. |
3. Customize your variable names for your SQS.
As explained, when a dependency is created, SleakOps generates a vargroup to hold all the needed attributes. In this step you can change the name of the attributes in case it is needed. SleakOps completes the values automatically. After this step, your dependency is created.
