OVA - Deployment

[c-bordon]

Implementation Plan

The initial implementation plan covers the following steps sequentially:

1. Upgrade the OVA base OS and the Build OVA workflow to use AL2023 #147
   Change the OVA Base OS from AL2 to AL2023.

2. Create OVA and AMI Configuration Modules #157
   After changing the OS, the next step is to implement the modules responsible for provisioning and configuring the Wazuh components, establishing a logic that allows the creation of a functional Wazuh OVA. (SPIKE - AMI #120 (comment))
   2.1. Provisioner
   This will be the first module to configure. It is responsible for installing the central Wazuh components on an instance (previously created using the allocator), including the cert-tool and the necessary dependencies for each component.

   2.2. Configurer
   Once the Provisioner module is implemented, the Configurer module must be created. This module is responsible for configuring all Wazuh components to ensure their proper functionality.

   The Configurer module will have three submodules, each handling specific configurations depending on the target use case (SPIKE - AMI #120 (comment)):

   • Installation Assistant: This submodule is responsible for configuring everything previously handled by the installation assistant.
   • OVA: This submodule configures everything related to the generation of the OVA. (Note: This submodule is not part of the AMI implementation but rather the OVA implementation).
   • AMI: This submodule is responsible for configuring everything related to the generation of the AMI.

3. OVA - Testing #181
   The testing phase will consist of two types of tests:
   3.1. Logic testing: Ensures that the logic behaves as expected. Depending on the input data, it checks that the correct functions are called, the necessary data is generated, etc.
   3.2. VM functionality testing: Ensures that, once the VM is created and configured, everything works as it should:

   • The provisioner installs the requested packages correctly.
   • The configurer sets up all the components correctly. This includes verifying the state, checking for error messages in logs, ensuring proper API connectivity, verifying certificates are created, and confirming correct connectivity with Filebeat.

4. OVA - Documentation #193

   • Modification of the documentation for the use of the Wazuh OVA, according to the changes generated in it during the overhaul process

Related

• SPIKE - OVA #119

[CarlosALgit]

Update Report

This week I have been working on the migration from Bash to Python of the scripts that generate the Amazon Linux 2023 Vagrant box.
For this, besides migrating the scripts directly the idea is to give them a structure to make them easier to modify in the future. In this way, I have also added some auxiliary functions and a folder structure.

I have also been testing and adapting this module to be used through Hatch taking advantage of the development made by @Enaraque here.

Next week I will have to develop the functions that install the dependencies and tools needed for the operation of these scripts on the host machine and with this the development of the logic of the OVA pre_configurer module will be finished (in the absence of testing and documentation).