Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MVP - AMI - Creation of the Configurer submodule #162

Open
Enaraque opened this issue Jan 14, 2025 · 0 comments
Open

MVP - AMI - Creation of the Configurer submodule #162

Enaraque opened this issue Jan 14, 2025 · 0 comments
Labels
level/subtask Subtask issue type/enhancement Enhancement issue

Comments

@Enaraque
Copy link
Member

Enaraque commented Jan 14, 2025

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:

  1. Customize a base AMI using the initial configuration files.
  2. Configure Wazuh's main components in the AMI using the core_configurer.
  3. 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.
  • (to be defined).

Related issue

DRI

@teddytpc1

@Enaraque Enaraque added level/task Task issue type/enhancement Enhancement issue level/subtask Subtask issue and removed level/task Task issue labels Jan 14, 2025
@teddytpc1 teddytpc1 changed the title MVP - Creation of the AMI Configurer submodule MVP - AMI - Creation of the Configurer submodule Jan 22, 2025
@wazuhci wazuhci moved this to Backlog in XDR+SIEM/Release 5.0.0 Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/subtask Subtask issue type/enhancement Enhancement issue
Projects
Status: Backlog
Development

No branches or pull requests

1 participant