Zip Installation Guide
Gigí Ruais
Wazuh is a security platform that provides unified XDR and SIEM protection for endpoints and cloud workloads. The solution is composed of a single universal agent and three central components: the Wazuh server, the Wazuh indexer, and the Wazuh dashboard. For more information, check the Getting Started documentation.
In this installation guide, you will learn how to install Wazuh in your infrastructure. We also offer Wazuh Cloud, our software as a service (SaaS) solution. Wazuh cloud is ready to use, with no additional hardware or software required, driving down the cost and complexity. Check the Cloud service documentation for more information and take advantage of the Cloud trial to explore this service.
The Wazuh indexer and Wazuh server can be installed on a single host or be distributed in cluster configurations. You can choose between two installation methods for each Wazuh central component. Both options provide instructions to install the central components on a single host or on separate hosts.
For more deployment flexibility and customization, install the Wazuh central components by starting with the Wazuh indexer deployment. This deployment method allows the all-in-one installation, and the installation of the components on separate servers.
The Wazuh agent is a single and lightweight monitoring software. It is a multi-platform component that can be deployed to laptops, desktops, servers, cloud instances, containers, or virtual machines. It provides visibility into the endpoint's security by collecting critical system and application records, inventory data, and detecting anomalies.
Wazuh provides other installation alternatives. These are complementary to the installation methods of this installation guide. You will find instructions on how to deploy Wazuh using ready-to-use machines, containers, and orchestration tools. There is also information on how to install the solution offline, from sources, and with commercial options.
This document is a guide for installing Arch Linux using the live system booted from an installation medium made from an official installation image. The installation medium provides accessibility features which are described on the page Install Arch Linux with accessibility options. For alternative means of installation, see Category:Installation process.
Before installing, it would be advised to view the FAQ. For conventions used in this document, see Help:Reading. In particular, code examples may contain placeholders (formatted in italics) that must be replaced manually.
This guide is kept concise and you are advised to follow the instructions in the presented order per section. For more detailed instructions, see the respective ArchWiki articles or the various programs' man pages, both linked from this guide. For interactive help, the IRC channel and the forums are also available.
Arch Linux should run on any x86_64-compatible machine with a minimum of 512 MiB RAM, though more memory is needed to boot the live system for installation.[1] A basic installation should take less than 2 GiB of disk space. As the installation process needs to retrieve packages from a remote repository, this guide assumes a working internet connection is available.
The ISO can be supplied to the target machine via a USB flash drive, an optical disc or a network with PXE: follow the appropriate article to prepare yourself an installation medium from the ISO file.
Console fonts are located in /usr/share/kbd/consolefonts/ and can likewise be set with setfont(8) omitting the path and file extension. For example, to use one of the largest fonts suitable for HiDPI screens, run:
If the command returns 64, then system is booted in UEFI mode and has a 64-bit x64 UEFI. If the command returns 32, then system is booted in UEFI mode and has a 32-bit IA32 UEFI; while this is supported, it will limit the boot loader choice to systemd-boot and GRUB. If the file does not exist, the system may be booted in BIOS (or CSM) mode. If the system did not boot in the mode you desired (UEFI vs BIOS), refer to your motherboard's manual.
Packages to be installed must be downloaded from mirror servers, which are defined in /etc/pacman.d/mirrorlist. On the live system, after connecting to the internet, reflector updates the mirror list by choosing 20 most recently synchronized HTTPS mirrors and sorting them by download rate.
The higher a mirror is placed in the list, the more priority it is given when downloading a package. You may want to inspect the file to see if it is satisfactory. If it is not, edit the file accordingly, and move the geographically closest mirrors to the top of the list, although other criteria should be taken into account.
The base package does not include all tools from the live installation, so installing more packages may be necessary for a fully functional base system. To install other packages or package groups, append the names to the pacstrap command above (space separated) or use pacman to install them while chrooted into the new system. In particular, consider installing:
Complete the network configuration for the newly installed environment. That may include installing suitable network management software, configuring it if necessary and enabling its systemd unit so that it starts at boot.
Finally, restart the machine by typing reboot: any partitions still mounted will be automatically unmounted by systemd. Remember to remove the installation medium and then login into the new system with the root account.
It covers installation procedures, including software verificationand subsequent steps for software installation and management. Additionally,IT administrators can refer to detailed instructions for full system softwareand firmware installation on a bare metal system, ensuring seamless platform upgrade and maintenance.
Moreover, Docker Engine depends on containerd and runc. Docker Enginebundles these dependencies as one bundle: containerd.io. If you haveinstalled the containerd or runc previously, uninstall them to avoidconflicts with the versions bundled with Docker Engine.
Images, containers, volumes, and networks stored in /var/lib/docker/ aren'tautomatically removed when you uninstall Docker. If you want to start with aclean installation, and prefer to clean up any existing data, read theuninstall Docker Engine section.
If you can't use Docker's apt repository to install Docker Engine, you candownload the deb file for your release and install it manually. You need todownload a new file each time you want to upgrade Docker Engine.
Docker provides a convenience script at to install Docker intodevelopment environments non-interactively. The convenience script isn'trecommended for production environments, but it's useful for creating aprovisioning script tailored to your needs. Also refer to theinstall using the repository steps to learnabout installation steps to install using the package repository. The source codefor the script is open source, and you can find it in thedocker-install repository on GitHub.
You have now successfully installed and started Docker Engine. The dockerservice starts automatically on Debian based distributions. On RPM baseddistributions, such as CentOS, Fedora, RHEL or SLES, you need to start itmanually using the appropriate systemctl or service command. As the messageindicates, non-root users can't run Docker commands by default.
The installation script requires root or sudo privileges to install anduse Docker. If you want to grant non-root users access to Docker, refer to thepost-installation steps for Linux.You can also install Docker without root privileges, or configured to run inrootless mode. For instructions on running Docker in rootless mode, refer torun the Docker daemon as a non-root user (rootless mode).
Docker also provides a convenience script at to install pre-releases ofDocker on Linux. This script is equal to the script at get.docker.com, butconfigures your package manager to use the test channel of the Docker packagerepository. The test channel includes both stable and pre-releases (betaversions, release-candidates) of Docker. Use this script to get early access tonew releases, and to evaluate them in a testing environment before they'rereleased as stable.
If you installed Docker using the convenience script, you should upgrade Dockerusing your package manager directly. There's no advantage to re-running theconvenience script. Re-running it can cause issues if it attempts to re-installrepositories which already exist on the host machine.
This topic describes how to install or update the latest release of the AWS Command Line Interface (AWS CLI) on supported operating systems. For information on the latest releases of AWS CLI, see the AWS CLI version 2 Changelog on GitHub.
The following are quick installation steps in a single copy and paste group based on whether you use 64-bit Linux or Linux ARM that provide a basic installation. For guided instructions, see the steps that follow.
(Optional) The following command block downloads and installs the AWS CLI without first verifying the integrity of your download. To verify the integrity of your download, use the below step by step instructions.
To update your current installation of the AWS CLI, add your existing symlink and installer information to construct the install command using the --bin-dir, --install-dir, and --update parameters. The following command block uses an example symlink of /usr/local/bin and example installer location of /usr/local/aws-cli.
c80f0f1006