Migrating Agent from mTLS to API Keys
Starting with agent version 1.14.0, Agent API Keys are the supported way of authenticating with Bigeye's systems. This guide discusses how to upgrade to use Agent API Keys.
- Provision an Agent API Key.
- Get the latest agent version.
- If your
docker-compose.yaml
file sayslatest
at the end of theimage
line, then you can simply run the following to pull the latest image:docker compose stop
thendocker compose pull
. - Otherwise, if you are pinning the version in your
docker-compose.yaml
file, then update the version number to1.14.0
- If your
# ...
services:
bigeye-agent:
# before
image: "docker.io/bigeyedata/agent:[previous version]"
# after
image: "docker.io/bigeyedata/agent:1.14.0"
- Update your
agent_config/agent_yaml
file.
# Before - these settings configured mTLS
mutualTlsEnabled: true
mtlsCertLocation: /app/config/mtls.pem
mtlsKeyLocation: /app/config/mtls.key
# After - comment out MTLS settings and add agentApiKey
# mutualTlsEnabled: true
# mtlsCertLocation: /app/config/mtls.pem
# mtlsKeyLocation: /app/config/mtls.key
agentApiKey: bigeye_agent_REPLACE_WITH_YOUR_KEY
# Note: Do NOT delete the following settings. They are nearby, and are still required.
# Encryption Keys
publicEncryptionKeyDir: /app/config
privateEncryptionKeyPath: /app/config/private.pem
- Restart your agent:
docker compose stop
docker compose up -d
# After a minute or so, verify the agent is successfully running by inspecting its logs
docker compose logs
Updated 5 months ago