Skip to content

Update AutoOps for self-managed custom cert page #4156

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.

Sign up for GitHub

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
+40 −2
Open

Update AutoOps for self-managed custom cert page #4156

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ec08cac
Update AutoOps for self-managed custom cert page
wajihaparvez Nov 28, 2025
a1ddc32
add spaces
wajihaparvez Nov 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 39 additions & 1 deletion deploy-manage/monitor/autoops/autoops-sm-custom-certification.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,10 @@ products:

This error occurs because the machine where you have installed {{agent}} does not trust your custom or internal CA. To fix this error, follow the steps on this page to configure the agent with your custom SSL certificate.

:::{note}
These instructions only apply to environments where [AutoOps {{agent}} is installed using Linux](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#install-agent).
Copy link
Contributor Author

@wajihaparvez wajihaparvez Nov 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@arnonst Is this the kind of phrasing you were looking for? What should we do about other installation methods?

:::

## Add custom certificate path to the `elastic-agent.yml` file

To configure {{agent}} with your custom SSL certificate, add the path to your certificate to the [`elastic-agent.yml`](/reference/fleet/configure-standalone-elastic-agents.md) policy file on the host machine where the agent is installed.
Expand All @@ -46,6 +50,40 @@ Complete the following steps:
- ${env:AUTOOPS_CA_CERT}
```
After adding this line to both modules, make sure the` AUTOOPS_CA_CERT` environment variable is set on the host machine and contains the full path to your certificate file (for example: `/etc/ssl/certs/my_internal_ca.crt`).

The following codeblock shows what your final configuration should look like when you use the environment variable method.

```yaml
receivers:
metricbeatreceiver:
metricbeat:
modules:
# Metrics
- module: autoops_es
hosts: ${env:AUTOOPS_ES_URL}
period: 10s
metricsets:
- cat_shards
- cluster_health
- cluster_settings
- license
- node_stats
- tasks_management
# --- ADD THIS LINE ---
ssl.certificate_authorities:
- ${env:AUTOOPS_CA_CERT}
# Templates
- module: autoops_es
hosts: ${env:AUTOOPS_ES_URL}
period: 24h
metricsets:
- cat_template
- component_template
- index_template
# --- ADD THIS LINE ---
ssl.certificate_authorities:
- ${env:AUTOOPS_CA_CERT}
```
::::

::::{tab-item} Hardcode file path
Expand Down Expand Up @@ -106,7 +144,7 @@ Complete the following steps:
```
6. Check the agent logs again to confirm that the error is gone and that {{agent}} has successfully connected your self-managed cluster to AutoOps.

:::{note}
:::{tip}
If you encounter the following error in the agent logs, there might be a formatting issue in the `elastic-agent.yml` file.
```sh
... can not convert 'object' into 'string' ... ssl.certificate_authorities ...
Expand Down
Loading