Traffic Data Sources

Kubernetes Daemonset

You can deploy Akto in Kubernetes and collect traffic through a daemonset on your Kubernetes configuration.

OpenShift

OpenShift should be used as a traffic connector if you are deploying and managing containerized applications using OpenShift.

eBPF

Akto-eBPF setup is recommended for mTLS systems when TLS termination happens at a proxy.

eBPF on mTLS

Akto-eBPF-mTLS setup is recommended for mTLS systems where TLS termination occurs at the application.

Apigee

Apigee setup is recommended if you are using Google's Apigee API Management platform to design, secure, and scale your APIs.

Cloudflare

You should use Cloudflare as a traffic connector if you are leveraging Cloudflare's CDN and security features to manage and optimize your API traffic.

F5

F5 setup is recommended if you are using F5's BIG-IP as an API gateway or load balancer to manage and control your API traffic.

Kong Mesh

Use this set-up if you are utilizing Kong's service mesh capabilities to manage and secure your microservices and APIs.

Layer 7

Layer7 is recommended if you are using CA Technologies' Layer7 API Management for securing and managing your APIs.

3Scale

This setup is recommended if your APIs are managed by 3scale.

NGINX

This setup is recommended if your APIs are routed by NGINX.

HA Proxy

HA Proxy should be used as a traffic connector if you are leveraging HA Proxy for load balancing, high availability, and proxying HTTP and TCP-based applications.

Envoy

Akto-Envoy setup is recommended if your APIs are routed by Envoy.

Istio

Akto-Istio setup is recommended if your APIs are routed by Istio.

Kong

Kong Gateway is an open source API gateway, built for multi-cloud and hybrid, and optimized for microservices and distributed architectures.

IBM API Connect

This setup is recommended if your APIs are managed by IBM API Connect

Citrix

Citrix setup is recommended if you are using ADC (NetScaler) to manage, secure, and optimize your API traffic.

Azure App Services

Azure App Services setup is recommended if you are using Microsoft's web app service with sidecar containers to collect and analyze your API traffic.

MuleSoft

Mulesoft setup is recommended if you are using API management and ESB capabilities to manage, secure, and analyze your APIs.

AWS Mirroring

You can deploy Akto in AWS and collect traffic through traffic mirroring.

GCP Mirroring

This setup only takes ten minutes. Once you connect GCP, Akto will process GCP traffic to create an API Inventory in real time.

AWS API Gateway

Akto-AWS-API-Gateway setup is recommended if you are using AWS API Gateway.

AWS EKS

You can deploy Akto in AWS and collect traffic through a daemonset on your AWS EKS configuration.

AWS Fargate

AWS Fargate allows you to use Amazon ECS to run containers without having to manage servers or clusters of Amazon EC2 instances.

AWS Beanstalk

You can deploy Akto in AWS and collect traffic through mirroring on your AWS Beanstalk setup.

AWS ECS

You can deploy Akto in AWS and collect traffic through containers on your AWS ECS cluster.

GCP Mirroring

This setup only takes ten minutes. Once you connect GCP, Akto will process GCP traffic to create an API Inventory in real time.

Apigee

Apigee setup is recommended if you are using Google's Apigee API Management platform to design, secure, and scale your APIs.

Google Cloud Run Functions

This setup is recommended if your applications are deployed using Google Cloud Run Functions.

Google Cloud Run

Google Cloud Run setup is recommended if you are using Google's serverless platform.

GKE

This setup is recommended if you are running containerized applications on Google Kubernetes Engine.

Azure App Services

Azure App Services setup is recommended if you are using Microsoft's web app service with sidecar containers to collect and analyze your API traffic.

Azure API Mangement

This setup is recommended if you are using Azure's API Management service to manage, secure, and analyze your APIs.

AKS

This setup is recommended if you are deploying applications on Azure Kubernetes Service.

Azure OpenShift

Azure OpenShift setup is recommended if your containerized applications are running on Azure Red Hat OpenShift.

Azure Container App

This setup is recommended if your applications are deployed using Azure Container Apps.

Azure Functions

Azure Functions setup is recommended if you are using Azure's serverless compute service.

Go

Use where Go-based services are deployed.

Java

You can use Akto's Java agent to capture API traffic directly from your Java applications.

NodeJS

This setup is ideal for environments where NodeJS-based services are deployed, ensuring seamless integration and real-time traffic monitoring.

Python

Use where Python-based services are deployed.

Docker

This setup is recommended only if other setups for AWS or GCP don't work.

TCP Agent

This setup is recommended only if other setups for AWS or GCP do not work.

API inventory from source code

Create API inventory from your source code using our code analysis tool.

GitHub

We recommend setting up GitHub if you want to connect and retrieve APIs directly from your source code hosted on GitHub.

GitLab

We recommend setting up GitLab if you want to connect and retrieve APIs directly from your source code hosted on GitLab.

Bitbucket

We recommend setting up Bitbucket if you want to connect and retrieve APIs directly from your source code hosted on Bitbucket.

Burp Suite

You can deploy Akto on your machine and download Akto's Burp extension to collect API traffic.

Postman

This setup is recommended if you have updated API collections maintained in Postman.

Har File Upload

For a very quick view of your inventory, you can upload a HAR file that contains traffic to Akto.

OpenAPI

Upload Open API/Swagger specification file to Akto to create an API inventory.

SOAP API

Upload WSDL file using Postman to Akto to create an API inventory.