You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**Post-release**: Updated the *Deployment on Docker* documentation. ([#8793](https://github.com/wazuh/wazuh-documentation/pull/8793))
74
+
-**Post-release**: Updated the Windows logo in the documentation. ([#8804](https://github.com/wazuh/wazuh-documentation/pull/8804))
75
+
-**Post-release**: Updated the offline installation guide. ([#8803](https://github.com/wazuh/wazuh-documentation/pull/8803))
76
+
-**Post-release**: Updated the instruction and images in Wazuh server API getting started documentation to reflect the new navigation path (**Server management** > **Dev Tools**). ([#8811](https://github.com/wazuh/wazuh-documentation/pull/8811))
Copy file name to clipboardExpand all lines: source/deployment-options/offline-installation/index.rst
+30-20Lines changed: 30 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,10 +3,10 @@
3
3
.. meta::
4
4
:description: Discover the offline step-by-step process to install the Wazuh central components without connection to the Internet.
5
5
6
-
Offline installation
7
-
====================
6
+
Offline installation guide
7
+
==========================
8
8
9
-
You can install Wazuh even when there is no connection to the Internet. Installing the solution offline involves downloading the Wazuh central components later to install them on a system with no Internet connection. The Wazuh server, the Wazuh indexer, and the Wazuh dashboard can be installed and configured on the same host in an all-in-one deployment, or each component can be installed on a separate host as a distributed deployment, depending on your environment's needs. The supported architecture is 64-bit (x86_64/AMD64 or AARCH64/ARM64).
9
+
You can install Wazuh even without an Internet connection. Installing the solution offline involves first downloading the Wazuh central components on a system with Internet access, then transferring and installing them on the offline system. Wazuh supports both all-in-one and distributed deployments. The Wazuh server, indexer, and dashboard can run on the same host in an all-in-one setup, or be installed on separate hosts for a distributed deployment. It supports 64-bit architectures, including x86_64/AMD64 and AARCH64/ARM64.
10
10
11
11
For more information about the hardware requirements and the recommended operating systems, check the :ref:`Requirements <installation_requirements>` section.
12
12
@@ -22,56 +22,65 @@ Prerequisites
22
22
Download the packages and configuration files
23
23
---------------------------------------------
24
24
25
-
#. Run the following commands from any Linux system with Internet connection. This action executes a script that downloads all required files for the offline installation (on x86_64/AMD64 and AARCH64/ARM64 architectures). Select the package format to download.
25
+
From a Linux system with Internet access, run the script below to download all files needed for offline installation. Choose the package format (RPM or DEB) and architecture (x86_64/AMD64 or AARCH64/ARM64).
26
+
27
+
#. Run the command on any Linux system with Internet access to download and prepare the Wazuh offline installer script
#. Edit ``config.yml`` to prepare the certificates creation.
64
74
65
75
- If you are performing an all-in-one deployment, replace ``"<indexer-node-ip>"``, ``"<wazuh-manager-ip>"``, and ``"<dashboard-node-ip>"`` with ``127.0.0.1``.
66
76
67
-
- If you are performing a distributed deployment, replace the node names and IP values with the corresponding names and IP addresses. You need to do this for all the Wazuh server, the Wazuh indexer, and the Wazuh dashboard nodes. Add as many node fields as needed.
77
+
- If you are performing a distributed deployment, replace the node names and IP values with the corresponding names and IP addresses. You need to do this for all the Wazuh server, Wazuh indexer, and Wazuh dashboard nodes. Add as many node fields as needed.
68
78
79
+
#. Run the ``./wazuh-install.sh -g`` command to create the certificates. For a multi-node cluster, these certificates need to be later deployed to all Wazuh instances in your cluster.
69
80
70
-
#. Run the ``./wazuh-install.sh -g`` to create the certificates. For a multi-node cluster, these certificates need to be later deployed to all Wazuh instances in your cluster.
81
+
.. code-block:: console
71
82
72
-
.. code-block:: console
73
-
74
-
# ./wazuh-install.sh -g
83
+
# ./wazuh-install.sh -g
75
84
76
85
#. Copy or move the following files to a directory on the host(s) from where the offline installation will be carried out. You can use ``scp`` for this.
77
86
@@ -84,6 +93,7 @@ Next steps
84
93
85
94
Once the Wazuh files are ready and copied to the specified hosts, it is necessary to install the Wazuh components.
86
95
96
+
Please make sure that a copy of the ``wazuh-install-files.tar`` and ``wazuh-offline.tar.gz`` files, created during the initial configuration step, is placed in your working directory.
Install and configure the different Wazuh components on a 64-bit (x86_64/AMD64 or AARCH64/ARM64) architecture with the aid of the Wazuh installation assistant.
4
+
Single-node offline installation
5
+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
6
+
7
+
Install and configure the single-node server on a 64-bit (x86_64/AMD64 or AARCH64/ARM64) architecture with the aid of the Wazuh assisted installation method.
5
8
6
9
.. note:: You need root user privileges to run all the commands described below.
7
10
8
11
Please, make sure that a copy of the ``wazuh-install-files.tar`` and ``wazuh-offline.tar.gz`` files, created during the initial configuration step, is placed in your working directory.
9
12
13
+
The following dependencies must be installed on the Wazuh single node.
14
+
15
+
.. tabs::
16
+
17
+
.. group-tab:: RPM
18
+
19
+
- coreutils
20
+
- libcap
21
+
22
+
.. group-tab:: DEB
23
+
24
+
- debconf
25
+
- adduser
26
+
- procps
27
+
- apt-transport-https
28
+
- gnupg
29
+
- debhelper (version 9 or later)
30
+
- libcap2-bin
31
+
32
+
#. To perform the offline installation with the ``--offline-installation`` of Wazuh server on a single-node using the assisted method, run:
33
+
34
+
.. code-block:: console
35
+
36
+
# bash wazuh-install.sh --offline-installation -a
37
+
38
+
Once the installation is finished, the output shows the access credentials and a message that confirms that the installation was successful.
39
+
40
+
.. code-block:: none
41
+
:emphasize-lines: 3,4
42
+
43
+
INFO: --- Summary ---
44
+
INFO: You can access the web interface https://<WAZUH_DASHBOARD_IP_ADDRESS>
45
+
User: admin
46
+
Password: <ADMIN_PASSWORD>
47
+
INFO: Installation finished.
48
+
49
+
#. Access the Wazuh web interface with your admin user credentials. This is the default administrator account for the Wazuh indexer and it allows you to access the Wazuh dashboard.
50
+
51
+
- **URL**: ``https://<WAZUH_NODE_IP_ADDRESS>``
52
+
- **Username**: ``admin``
53
+
- **Password**: ``<ADMIN_PASSWORD>``
54
+
55
+
Multi-node offline installation
56
+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
57
+
10
58
Installing the Wazuh indexer
11
-
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
59
+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
60
+
61
+
Install and configure the Wazuh indexer nodes on a 64-bit (x86_64/AMD64 or AARCH64/ARM64) architecture.
12
62
13
-
Install and configure the Wazuh indexer nodes.
63
+
The following dependencies must be installed on the Wazuh indexer nodes.
14
64
15
65
.. tabs::
16
66
17
67
.. group-tab:: RPM
18
68
19
-
The following dependencies must be installed on the Wazuh indexer nodes.
20
-
21
69
- coreutils
22
70
23
71
.. group-tab:: DEB
24
72
25
-
The following dependencies must be installed on the Wazuh indexer nodes.
26
-
27
73
- debconf
28
74
- adduser
29
75
- procps
30
76
- apt-transport-https
31
77
32
-
#. Run the assistant with the ``--offline-installation`` to perform an offline installation. Use the option ``--wazuh-indexer`` and the node name to install and configure the Wazuh indexer. The node name must be the same one used in ``config.yml`` for the initial configuration, for example, ``node-1``.
78
+
#. Run the multi-node assisted method with the ``--offline-installation`` to perform an offline installation. Use the option ``--wazuh-indexer`` and the node name to install and configure the Wazuh indexer. The node name must be the same one used in ``config.yml`` for the initial configuration, for example, ``node-1``.
Repeat this step for every Wazuh indexer node in your cluster. Then proceed with initializing your single-node or multi-node cluster in the next step.
84
+
Repeat this step for every Wazuh indexer node in your cluster. Then proceed with initializing your multi-node cluster in the next step.
39
85
40
-
#. Run the Wazuh installation assistant with option ``--start-cluster`` on any Wazuh indexer node to load the new certificates information and start the cluster.
86
+
#. Run the Wazuh assisted installation option ``--start-cluster`` on any Wazuh indexer node to load the new certificates information and start the cluster.
41
87
42
88
.. code-block:: console
43
89
@@ -46,7 +92,7 @@ Install and configure the Wazuh indexer nodes.
46
92
.. note:: You only have to initialize the cluster `once`, there is no need to run this command on every node.
47
93
48
94
Testing the cluster installation
49
-
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
95
+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
50
96
51
97
#. Run the following command to get the *admin* password:
52
98
@@ -80,14 +126,14 @@ Testing the cluster installation
80
126
"tagline" : "The OpenSearch Project: https://opensearch.org/"
81
127
}
82
128
83
-
#. Replace ``<WAZUH_INDEXER_IP_ADDRESS>`` and ``<ADMIN_PASSWORD>``, and run the following command to check if the cluster is working correctly:
129
+
#. Verify that the cluster is running correctly. Replace ``<WAZUH_INDEXER_IP_ADDRESS>`` and ``<ADMIN_PASSWORD>`` in the following command, then execute it:
On systems with *apt* as package manager, the following dependencies must be installed on the Wazuh server nodes.
103
149
104
-
- gnupg
105
150
- apt-transport-https
151
+
- gnupg
106
152
107
-
#. Run the assistant with the ``--offline-installation`` to perform an offline installation. Use the option ``--wazuh-server`` followed by the node name to install the Wazuh server. The node name must be the same one used in ``config.yml`` for the initial configuration, for example, ``wazuh-1``.
153
+
#. Run the assisted method with ``--offline-installation`` to perform an offline installation. Use the option ``--wazuh-server`` followed by the node name to install the Wazuh server. The node name must be the same one used in ``config.yml`` for the initial configuration, for example, ``wazuh-1``.
- If you want a Wazuh server multi-node cluster, repeat this step on every Wazuh server node.
116
-
- If you want a Wazuh server single-node cluster, everything is set and you can proceed directly with the next stage.
159
+
Your Wazuh server is now successfully installed. Repeat this step on every Wazuh server node.
117
160
118
161
Installing the Wazuh dashboard
119
-
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
162
+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
163
+
164
+
The following dependencies must be installed on the Wazuh dashboard node.
120
165
121
166
.. tabs::
122
167
123
168
.. group-tab:: RPM
124
169
125
-
The following dependencies must be installed on the Wazuh dashboard node.
126
-
127
170
- libcap
128
171
129
172
.. group-tab:: DEB
130
173
131
-
The following dependencies must be installed on the Wazuh dashboard node.
132
-
133
-
- debhelper version 9 or later
174
+
- debhelper (version 9 or later)
134
175
- tar
135
176
- curl
136
177
- libcap2-bin
137
178
138
-
#. Run the assistant with the ``--offline-installation`` to perform an offline installation. Use the option ``--wazuh-dashboard`` and the node name to install and configure the Wazuh dashboard. The node name must be the same one used in ``config.yml`` for the initial configuration, for example, ``dashboard``.
179
+
#. Run the assisted method with ``--offline-installation`` to perform an offline installation. Use the option ``--wazuh-dashboard`` and the node name to install and configure the Wazuh dashboard. The node name must be the same one used in ``config.yml`` for the initial configuration, for example, ``dashboard``.
The default Wazuh web user interface port is 443, used by the Wazuh dashboard. You can change this port using the optional parameter ``-p|--port <PORT_NUMBER>``. Some recommended ports are 8443, 8444, 8080, 8888, and 9000.
185
+
The default TCP port for the Wazuh web user interface (dashboard) is 443. You can change this port using the optional parameter ``-p|--port <PORT_NUMBER>``. Some recommended ports are 8443, 8444, 8080, 8888, and 9000.
145
186
146
187
Once the assistant finishes the installation, the output shows the access credentials and a message that confirms that the installation was successful.
You can interact with the Wazuh server API via the Wazuh dashboard. To do this, you need to log into the Wazuh dashboard with a user that has administrator privileges. For example, the default ``admin`` user has administrator privileges. To access the Wazuh server API console on the dashboard, click on the menu icon and navigate to **Tools** > **API Console**.
33
+
You can interact with the Wazuh server API via the Wazuh dashboard. To do this, you need to log into the Wazuh dashboard with a user that has administrator privileges. For example, the default ``admin`` user has administrator privileges. To access the Wazuh server API console on the dashboard, click on the menu icon and navigate to **Server management** > **Dev Tools**.
0 commit comments