-
Notifications
You must be signed in to change notification settings - Fork 347
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch '4.9.1' into merge-4.9.1-into-4.10.0
- Loading branch information
Showing
30 changed files
with
265 additions
and
502 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,36 @@ | ||
| .. Copyright (C) 2015, Wazuh, Inc. | ||
| .. meta:: | ||
| :description: Check out how to configure a custom domain to access an environment in Wazuh Cloud. Learn more about it in this section of the documentation. | ||
|
|
||
| Custom DNS | ||
| ========== | ||
|
|
||
| By default, Wazuh Cloud environments are accessed through a subdomain of ``cloud.wazuh.com``. | ||
|
|
||
| You can configure your environment to use your own custom domain. To do this, go to the **Wazuh Cloud Console** under the environment details page. You need to provide the following: | ||
|
|
||
| - **Certificate**: SSL/TLS certificate for your domain | ||
|
|
||
| - Must use SHA2 | ||
| - Must use RSA with key size of at least 2048 bits | ||
| - TLS Web Server Authentication is required if using EKU | ||
| - Must contain domain name in CN or SAN field(s) | ||
| - Must be PEM encoded | ||
|
|
||
| - **Private Key**: Associated with the provided certificate | ||
|
|
||
| - Must not be encrypted or require a passphrase | ||
| - Must be PEM encoded | ||
|
|
||
| - **Certificate Chain**: Used to sign your certificate | ||
|
|
||
| - Must contain all intermediate certificates in the certificate chain | ||
| - Must be signed by a trusted certificate authority | ||
| - Must be PEM encoded | ||
|
|
||
| After providing the above and applying the configuration, create a ``CNAME`` DNS record using the value provided by the **Wazuh Cloud Console**. | ||
|
|
||
| .. note:: | ||
|
|
||
| Your Wazuh Cloud environment is still accessible through the default URL, even if you have configured a custom domain. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,20 +1,18 @@ | ||
| .. Copyright (C) 2015, Wazuh, Inc. | ||
| .. meta:: | ||
| :description: Learn how to migrate from Open Distro for Elasticsearch to the Wazuh indexer and Wazuh dashboard. This guide gives instructions to perform the migration. | ||
| Migration guide | ||
| ================ | ||
| .. meta:: | ||
| :description: Learn how to keep a backup of key files of your Wazuh installation. | ||
|
|
||
| From Wazuh 4.0.0 to Wazuh 4.2.7, the default Wazuh installation included the Wazuh server and `Open Distro for Elasticsearch <https://opendistro.github.io/for-elasticsearch/>`_, a project that is now archived and has been succeeded by OpenSearch. This guide includes instructions to migrate from Open Distro for Elasticsearch to the :doc:`Wazuh indexer </getting-started/components/wazuh-indexer>` and :doc:`Wazuh dashboard </getting-started/components/wazuh-dashboard>`, the new components introduced in Wazuh 4.3.0. | ||
| Backup guide | ||
| ============ | ||
|
|
||
| - :doc:`Migrating to the Wazuh indexer </migration-guide/wazuh-indexer>`: Follow this section to migrate from Open Distro for Elasticsearch 1.13 to the Wazuh indexer. This new component consists of a distribution of `Opensearch <https://github.com/opensearch-project/OpenSearch>`_ with additional tools that Wazuh has created to assist with the installation and configuration of the search engine. | ||
| In this section you can find instructions on how to create and restore a backup of your Wazuh installation. | ||
|
|
||
| - :doc:`Migrating to the Wazuh dashboard </migration-guide/wazuh-dashboard>`: This section will guide you through the migration from Open Distro for Elasticsearch Kibana 1.13 to the Wazuh dashboard. This new web interface for the Wazuh platform is a customized `OpenSearch Dashboards <https://github.com/opensearch-project/OpenSearch-Dashboards>`_ distribution that includes different sections, visualizations and tools to manage the Wazuh indexer information and the Wazuh Server. | ||
| To do this backup, you copy key files to a folder preserving file permissions, ownership, and path. Later, you can move this folder contents back to the corresponding location to restore your Wazuh data, certificates, and configurations. Backing up Wazuh files is useful in cases such as moving your Wazuh installation to another system. | ||
|
|
||
| .. toctree:: | ||
| :hidden: | ||
| :maxdepth: 2 | ||
|
|
||
| creating/index | ||
| restoring/index | ||
|
|
||
| wazuh-indexer | ||
| wazuh-dashboard | ||
| files-backup/index |
File renamed without changes.
Oops, something went wrong.