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
Within the Configurer module, a submodule named ami_configurer will be created. This submodule will handle all configurations necessary for integrating Wazuh and preparing it for deployment as an AMI.
The submodule will include two fundamental parts:
Base AMI Configuration Files: These files, referenced in the AMI spike, will configure a base instance from which all subsequent Wazuh configurations will build.
AMI Generation Configuration Files: These files, currently located in the ami directory, ensure that certificates meet AWS format requirements and that the dashboard password is replaced with the instance ID.
Initially, these files will already exist but need to be migrated to Python. This transition is crucial to create a more structured, maintainable, and testable environment, as the current Bash scripts are complex and less scalable.
Important
Additionally, configurations currently implemented through Ansible playbooks must also be transitioned to Python. This ensures Ansible is used only for copying files from the local machine to the remote machine and executing the Configurer.
By adapting these files to Python, we can establish a modular structure allowing us to:
Customize a base AMI using the initial configuration files.
Configure Wazuh's main components in the AMI using the core_configurer.
Prepare the AMI for proper generation and deployment.
Tests
Unit Tests
As the submodule is developed, unit tests must be written continuously to validate the correctness of each method and function.
The tests will use pytest, and overall test coverage will be monitored to ensure a significant percentage of the code is tested.
Deployment Tests
Deployment tests for the AMI configuration must verify that the AMI includes all necessary configurations specified in the configuration files, such as:
Wazuh logo displayed during the login session.
A wazuh-user account is created.
Hostname is updated appropriately.
Dashboard password is replaced with the instance ID.
Description
Within the Configurer module, a submodule named ami_configurer will be created. This submodule will handle all configurations necessary for integrating Wazuh and preparing it for deployment as an AMI.
The submodule will include two fundamental parts:
Base AMI Configuration Files: These files, referenced in the AMI spike, will configure a base instance from which all subsequent Wazuh configurations will build.
AMI Generation Configuration Files: These files, currently located in the
ami
directory, ensure that certificates meet AWS format requirements and that the dashboard password is replaced with the instance ID.Initially, these files will already exist but need to be migrated to Python. This transition is crucial to create a more structured, maintainable, and testable environment, as the current Bash scripts are complex and less scalable.
Important
Additionally, configurations currently implemented through Ansible playbooks must also be transitioned to Python. This ensures Ansible is used only for copying files from the local machine to the remote machine and executing the Configurer.
By adapting these files to Python, we can establish a modular structure allowing us to:
Tests
Unit Tests
As the submodule is developed, unit tests must be written continuously to validate the correctness of each method and function.
The tests will use
pytest
, and overall test coverage will be monitored to ensure a significant percentage of the code is tested.Deployment Tests
Deployment tests for the AMI configuration must verify that the AMI includes all necessary configurations specified in the configuration files, such as:
wazuh-user
account is created.Related issue
DRI
@teddytpc1
The text was updated successfully, but these errors were encountered: