Ansible Role: Elastic Container

An Ansible role that runs Elastic Container on a Linux system.

• Creates an agent policy
• Add 2 integrations to the policy (Elastic Defend and Windows)
• Configures one (1) Fleet server
• Downloads the compatible agent version and drops it inside the ludus host (/opt/ludus/resources/elastic) for "offline" agent installations.
• Reconfigures the output elasticsearch URL to be an array of the ipv4 address of this elastic server
• Writes the enrollment token to {{ ludus_elastic_container_install_path }}/enrollment_token.txt. With this token and the IP address assigned to the elastic server, you are ready to deploy agents.

Requirements

None.

Role Variables

Available variables are listed below, along with default values (see defaults/main.yml):

ludus_elastic_container_install_path: /opt/elastic_container
ludus_elastic_password: "elasticpassword"
ludus_elastic_stack_version: "8.12.2"
elastic_container_branch: main

Dependencies

geerlingguy.docker

[Optional] Check out the .env example prior to uploading the role (if you choose to clone and add).

Example Playbook

- hosts: elastic-server
  roles:
    - badsectorlabs.ludus_elastic_container

Example Ludus Range Config

ludus:
  - vm_name: "{{ range_id }}-elastic-server"
    hostname: "{{ range_id }}-elastic-server"
    template: debian-12-x64-server-template
    vlan: 20
    ip_last_octet: 2
    ram_gb: 8
    cpus: 4
    linux: true
    testing:
      snapshot: false
      block_internet: false
    roles:
      - badsectorlabs.ludus_elastic_container
    role_vars:
      ludus_elastic_password: "hellofromtheotherside"

Ludus setup

# Add the role to your ludus host
ludus ansible roles add badsectorlabs.ludus_elastic_container

# Get your config into a file so you can assign to a VM
ludus range config get > config.yml

# Edit config to add the role to the VMs you wish to make an elastic server
ludus range config set -f config.yml

# Deploy the range with the user-defined-roles ONLY :)
ludus range deploy -t user-defined-roles

• Once deployed, access the kibana UI at https://<IP>:5601

• In Kibana UI, you can enable your own detection rules (to trigger alerts). No rules are enabled by default to allow the user to "control" the noise. This is a good reference on how to manage detection rules.

License

Apache-2.0

Author Information

This role was created by Bad Sector Labs, for Ludus.

Resources/Credits

• Excellent blog post from Elastic Security Labs
• This role heavily utilized this awesome project by @peasead
• Kibana Fleet API
• Elastic Integrations