# Specifying SSL settings for managed Metricbeat

**URL:** https://discuss.elastic.co/t/specifying-ssl-settings-for-managed-metricbeat/184601
**Category:** Beats
**Tags:** fleet
**Created:** [June 6, 2019, 2:07pm UTC](https://discuss.elastic.co/t/specifying-ssl-settings-for-managed-metricbeat/184601 "2019-06-06T14:07:34Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![bobes](https://avatars.discourse-cdn.com/v4/letter/b/bcef8e/32.png) [@bobes](https://discuss.elastic.co/u/bobes)
#### Post date: [June 6, 2019, 2:07pm UTC](https://discuss.elastic.co/t/specifying-ssl-settings-for-managed-metricbeat/184601/1 "2019-06-06T14:07:34Z")

</div>

I've enabled a Metricbeat to use CM, before I had configurations to deal with SSL in the YAML of the Beat. Now that its managed where do I define these settings? I attempted to define then in the metricbeat.yml file, but I think my formatting was off.

---

<div class="post-metadata">

### Author: ![bobes](https://avatars.discourse-cdn.com/v4/letter/b/bcef8e/32.png) [@bobes](https://discuss.elastic.co/u/bobes)
#### Post date: [June 6, 2019, 2:09pm UTC](https://discuss.elastic.co/t/specifying-ssl-settings-for-managed-metricbeat/184601/2 "2019-06-06T14:09:13Z")

</div>

This is what i attempted.

```
management:
  enabled: true
  period: 1m0s
  events_reporter:
    period: 30s
    max_batch_size: 1000
  access_token: ${management.accesstoken}
  kibana:
    protocol: https
    host: kibana.company.com
    ssl: null
    timeout: 10s
    ignoreversion: true
  blacklist:
    output: console|file

metricbeat.modules
-module: elasticsearch
  ssl.verification_mode: "none"
```

---

<div class="post-metadata">

### Author: ![bobes](https://avatars.discourse-cdn.com/v4/letter/b/bcef8e/32.png) [@bobes](https://discuss.elastic.co/u/bobes)
#### Post date: [June 6, 2019, 2:43pm UTC](https://discuss.elastic.co/t/specifying-ssl-settings-for-managed-metricbeat/184601/3 "2019-06-06T14:43:02Z")

</div>

Figured it out. it needs to be defined like this (leaving here in case someone else has the same issue). Doing this means you don't need to define the metricbeat module for elasticsearch in CM

```
management:
  enabled: true
  period: 1m0s
  events_reporter:
    period: 30s
    max_batch_size: 1000
  access_token: ${management.accesstoken}
  kibana:
    protocol: https
    host: kibana.company.com
    ssl: null
    timeout: 10s
    ignoreversion: true
  blacklist:
    output: console|file

metricbeat.modules:
- module: elasticsearch
  period: 10s
  metricsets: ["node_stats"]
  hosts: ["https://localhost:9200"]
  username: "user"
  password: "password"
  ssl.verification_mode: "none"
```

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 4, 2019, 2:43pm UTC](https://discuss.elastic.co/t/specifying-ssl-settings-for-managed-metricbeat/184601/4 "2019-07-04T14:43:13Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
