Connect Akto on TLS service
Last updated
Was this helpful?
Last updated
Was this helpful?
Akto can automatically detect and analyze your API traffic—even if it's encrypted using TLS. This is achieved using Akto Traffic Collector, which leverages eBPF to passively observe kernel-level network activity.
You can deploy this collector on any Linux-based system (VM, bare metal, or cloud instance) to forward traffic insights to Akto. Here's how:
First, set up and configure the Akto Traffic Processor (Mini-Runtime).
You’ll get a runtime service URL or Kafka IP once setup is complete.
If you're using on-prem Akto, this will be your internal runtime URL.
📘 for instructions.
This Docker container uses eBPF to mirror all API traffic at the kernel level—including TLS-encrypted traffic—without needing to decrypt it manually or modify applications.
⚠ Prerequisites:
Linux VM or system with kernel headers installed (required for eBPF)
Docker daemon installed and running
Access to your Akto runtime (Kafka IP)
The kafka_ip here is the mini-runtime/runtime service URL we saved in the previous step.
In case you face an issue with the spaces in the command above
eBPF hooks into your Linux kernel to capture real-time traffic—even if it’s encrypted (TLS).
No code changes, no traffic proxying, no SSL termination.
The collector forwards API traces to Akto for real-time inventory and security analysis.
There are multiple ways to request support from Akto. We are 24X7 available on the following:
In-app intercom
support. Message us with your query on intercom in Akto dashboard and someone will reply.
Contact help@akto.io
for email support.
Join our for community support.
Contact us .