Akto - API Security platform

Akto Website Start free Book a demo Discord GitHub

Github Open Source Repo
What is Akto?
AktoGPT
Getting Started
Traffic Connector
API Inventory
- Concepts
- How-To
API Protection
- Overview
- Concepts
  - Threat Policy
WAF
- AWS WAF
- Cloudflare WAF
Test Editor
- Concepts
- How To
API Security Testing
- Concepts
- How To
Issues
- Concepts
- How To
CI/CD
Account
Compliance
- Concepts
  - Overview
API security posture
- Concepts
  - Overview
SIEM Integration
- Splunk
Alerts
Pricing
- Pricing Plans
- How To
API reference
- API reference
Components
Troubleshooting
Stay Updated on New Releases
Support

Powered by GitBook

On this page

Kubernetes
API Gateways
Mirroring
AWS Services
GCP Services
Azure Services
Akto SDK
Virtual Machines
Source Code
Manual

Was this helpful?

Traffic Connector

Traffic Data Sources

PreviousFAQs on data concerns NexteBPF

Last updated 8 days ago

Was this helpful?

Kubernetes

API Gateways

Mirroring

AWS Services

GCP Services

Azure Services

Akto SDK

Virtual Machines

Source Code

Manual

Cover

Kubernetes Daemonset

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

Cover

OpenShift

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

Cover

eBPF

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

Cover

eBPF on mTLS

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

Cover

Apigee

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

Cover

Azure API Gateway

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

Cover

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.

Cover

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.

Cover

Kong Mesh

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

Cover

Layer 7

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

Cover

3Scale

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

Cover

NGINX

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

Cover

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.

Cover

Envoy

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

Cover

Istio

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

Cover

Kong

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

Cover

IBM API Connect

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

Cover

Citrix

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

Cover

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.

Cover

MuleSoft

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

Cover

AWS Mirroring

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

Cover

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.

Cover

AWS API Gateway

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

Cover

AWS EKS

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

Cover

AWS Fargate

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

Cover

AWS Beanstalk

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

Cover

AWS ECS

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

Cover

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.

Cover

Apigee

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

Cover

Google Cloud Run Functions

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

Cover

Google Cloud Run

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

Cover

GKE

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

Cover

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.

Cover

Azure API Mangement

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

Cover

AKS

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

Cover

Azure OpenShift

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

Cover

Azure Container App

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

Cover

Azure Functions

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

Cover

Go

Use where Go-based services are deployed.

Cover

Java

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

Cover

NodeJS

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

Cover

Python

Use where Python-based services are deployed.

Cover

Docker

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

Cover

TCP Agent

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

Cover

API inventory from source code

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

Cover

GitHub

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

Cover

GitLab

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

Cover

Bitbucket

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

Cover

Burp Suite

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

Cover

Postman

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

Cover

Har File Upload

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

Cover

OpenAPI

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

Cover

SOAP API

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