cloudbeat.yml

###################### Cloudbeat Configuration Example #########################

# This file is an example configuration file highlighting only the most common
# options. The cloudbeat.reference.yml file from the same directory contains all the
# supported options with more comments. You can use it as a reference.
#
# You can find the full configuration reference here:
# https://www.elastic.co/guide/en/beats/cloudbeat/index.html

# For more available modules and options, please see the cloudbeat.reference.yml sample
# configuration file.

cloudbeat:
  type: cloudbeat/cis_k8s
  # Defines how often an event is sent to the output
  period: 4h
  fetchers:
    - name: kube-api
    - name: process
      directory: "/hostfs"
      processes:
        etcd:
        kube-apiserver:
        kube-controller:
        kube-scheduler:
        kubelet:
          config-file-arguments:
            - config
    - name: file-system
      patterns: [
        "/hostfs/etc/kubernetes/scheduler.conf",
        "/hostfs/etc/kubernetes/controller-manager.conf",
        "/hostfs/etc/kubernetes/admin.conf",
        "/hostfs/etc/kubernetes/kubelet.conf",
        "/hostfs/etc/kubernetes/manifests/etcd.yaml",
        "/hostfs/etc/kubernetes/manifests/kube-apiserver.yaml",
        "/hostfs/etc/kubernetes/manifests/kube-controller-manager.yaml",
        "/hostfs/etc/kubernetes/manifests/kube-scheduler.yaml",
        "/hostfs/etc/systemd/system/kubelet.service.d/10-kubeadm.conf",
        "/hostfs/etc/kubernetes/pki/*",
        "/hostfs/var/lib/kubelet/config.yaml",
        "/hostfs/var/lib/etcd",
        "/hostfs/etc/kubernetes/pki"
      ]
  config:
    v1:
      benchmark: cis_k8s
#    # EKS Fetchers configuration
#      - name: kube-api
#      - name: process
#        directory: "/hostfs"
#        processes:
#          kubelet:
#            config-file-arguments:
#              - config
#      - name: aws-ecr
#      - name: aws-elb
#      - name: file-system
#        patterns: [
#          "/hostfs/etc/kubernetes/kubelet/kubelet-config.json",
#          "/hostfs/var/lib/kubelet/kubeconfig",
#        ]


# ================================== General ===================================

# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
#name:

# The tags of the shipper are included in their own field with each
# transaction published.
#tags: ["service-X", "web-tier"]

# Optional fields that you can specify to add additional information to the
# output.
#fields:
#  env: staging

# ================================= Dashboards =================================
# These settings control loading the sample dashboards to the Kibana index. Loading
# the dashboards is disabled by default and can be enabled either by setting the
# options here or by using the `setup` command.
#setup.dashboards.enabled: false

# The URL from where to download the dashboards archive. By default this URL
# has a value which is computed based on the Beat name and version. For released
# versions, this URL points to the dashboard archive on the artifacts.elastic.co
# website.
#setup.dashboards.url:

# =================================== Kibana ===================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:

  # Kibana Host
  # Scheme and port can be left out and will be set to the default (http and 5601)
  # In case you specify and additional path, the scheme is required: http://localhost:5601/path
  # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
  #host: "localhost:5601"

  # Kibana Space ID
  # ID of the Kibana Space into which the dashboards should be loaded. By default,
  # the Default Space will be used.
  #space.id:

# =============================== Elastic Cloud ================================

# These settings simplify using Cloudbeat with the Elastic Cloud (https://cloud.elastic.co/).

# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
# `setup.kibana.host` options.
# You can find the `cloud.id` in the Elastic Cloud web UI.
#cloud.id:

# The cloud.auth setting overwrites the `output.elasticsearch.username` and
# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
#cloud.auth:

# ================================== Outputs ===================================

# Configure what output to use when sending the data collected by the beat.

# ---------------------------- Elasticsearch Output ----------------------------
output.elasticsearch:
  # Array of hosts to connect to.
  hosts: ["localhost:9200"]

  # Protocol - either `http` (default) or `https`.
  #protocol: "https"

  # Authentication credentials - either API key or username/password.
  #api_key: "id:api_key"
  #username: "elastic"
  #password: "changeme"

# ------------------------------ Logstash Output -------------------------------
#output.logstash:
  # The Logstash hosts
  #hosts: ["localhost:5044"]

  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]

  # Certificate for SSL client authentication
  #ssl.certificate: "/etc/pki/client/cert.pem"

  # Client Certificate Key
  #ssl.key: "/etc/pki/client/cert.key"

# ================================= Processors =================================

# Configure processors to enhance or manipulate events generated by the beat.

processors:
  - add_host_metadata: ~
  - add_cloud_metadata: ~
  - add_docker_metadata: ~
  # in case you run in EKS/Kubernetes environment, you can use the following processor to add cluster id
#  - add_cluster_id: ~

# ================================== Logging ===================================

# Sets log level. The default log level is info.
# Available log levels are: error, warning, info, debug
#logging.level: debug

# At debug level, you can selectively enable logging only for some components.
# To enable all selectors use ["*"]. Examples of other selectors are "beat",
# "publisher", "service".
#logging.selectors: ["*"]

# ============================= X-Pack Monitoring ==============================
# Cloudbeat can export internal metrics to a central Elasticsearch monitoring
# cluster.  This requires xpack monitoring to be enabled in Elasticsearch.  The
# reporting is disabled by default.

# Set to true to enable the monitoring reporter.
#monitoring.enabled: false

# Sets the UUID of the Elasticsearch cluster under which monitoring data for this
# Cloudbeat instance will appear in the Stack Monitoring UI. If output.elasticsearch
# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.
#monitoring.cluster_uuid:

# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch output are accepted here as well.
# Note that the settings should point to your Elasticsearch *monitoring* cluster.
# Any setting that is not set is automatically inherited from the Elasticsearch
# output configuration, so if you have the Elasticsearch output configured such
# that it is pointing to your Elasticsearch monitoring cluster, you can simply
# uncomment the following line.
#monitoring.elasticsearch:

# ============================== Instrumentation ===============================

# Instrumentation support for the cloudbeat.
#instrumentation:
    # Set to true to enable instrumentation of cloudbeat.
    #enabled: false

    # Environment in which cloudbeat is running on (eg: staging, production, etc.)
    #environment: ""

    # APM Server hosts to report instrumentation results to.
    #hosts:
    #  - http://localhost:8200

    # API Key for the APM Server(s).
    # If api_key is set then secret_token will be ignored.
    #api_key:

    # Secret token for the APM Server(s).
    #secret_token:


# ================================= Migration ==================================

# This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true