Connect Akto with Internet Information Services (IIS)
Microsoft IIS (Internet Information Services) is a widely used web server for hosting web applications on Windows. Integrating IIS with Akto enables you to automatically mirror API traffic (including headers and payloads) to the Akto backend, empowering deep visibility and continuous API security analysis.
To connect Akto with your IIS server, follow the steps below:
Step 1: Deploy the Akto Data-Ingestion Service
Before configuring the IIS Traffic Connector, you need to deploy the Akto Data-Ingestion Service. Ensure that the service is running and accessible via a publicly available URL.
1.1 Download the Required Files
SSH into the instance where you want to deploy the data-ingestion service and run these commands:
wget https://raw.githubusercontent.com/akto-api-security/infra/refs/heads/feature/quick-setup/docker-compose-mini-runtime-data-ingestion.yaml
wget https://raw.githubusercontent.com/akto-api-security/infra/refs/heads/feature/quick-setup/data-ingestion-docker.env
wget https://raw.githubusercontent.com/akto-api-security/infra/refs/heads/feature/quick-setup/docker-threat-detection.env
wget https://raw.githubusercontent.com/akto-api-security/infra/refs/heads/feature/quick-setup/docker-mini-runtime.env
wget https://raw.githubusercontent.com/akto-api-security/infra/refs/heads/feature/quick-setup/watchtower.env1.2 Retrieve the DATABASE_ABSTRACTOR_SERVICE_TOKEN
DATABASE_ABSTRACTOR_SERVICE_TOKENLog in to the Akto Dashboard
Navigate to the Quick Start tab in the left panel

Select Hybrid SaaS Connector

Copy the token from the Runtime Service Command section
1.3 Update the docker-mini-runtime.env File
docker-mini-runtime.env FileOpen the docker-mini-runtime.env file and replace token with the token you just copied:
1.4 Deploy the Data-Ingestion Service
Run the following command:
1.5 Note the IP Address of the Data-Ingestion Service
Ensure this IP is reachable from your IIS server. You will need this to forward the traffic data to Akto.
Step 2: Install the IIS Traffic Connector
Akto provides a native IIS module that can capture HTTP request and response headers and payloads. This module supports both 64-bit and 32-bit environments.
👉 Important: You must download and use only one DLL — either 64-bit or 32-bit depending on your system. Regardless of which one you choose, always rename it to AktoNativeIisTrafficCollector.dll, move it to C:\akto_configs, and use that same name everywhere.
2.1 Prepare Configuration File
Create a folder at the root of your C drive:
Inside it, create a file named
config.jsonwith the following content:Replace
DATA-INGESTION-SERVICE-URLwith the address of your deployed Akto ingestion service.Configuration Fields:
backendUrl- The URL of your Akto data-ingestion service endpointlogLevel- Controls the logging verbosity. Accepted values:INFO,WARN,NONE,ERROR, orDEBUGmaxPayloadSize- Maximum size (in bytes) of request + response to capture. Only traffic with total size less than this value will be captured. Example:1048576for 1MBmaxQueueSize- Maximum number of requests to store in memory before flushing to Akto. Controls memory usage and batch size
2.2 Install the Module Globally (Recommended)
You need to register the Akto IIS module globally so it applies to all websites.
Download the correct DLL for your environment (pick only one). You can also simply paste the link in browser and download the DLL file.
Open an elevated command prompt (Administrator) and run the following commands:
These commands:
Register the
AktoTrafficConnectormodule in IISAdd it for all sites so that traffic from every hosted website is mirrored
Explicitly add
AktoNativeIisTrafficCollectorto the global modules sectionList all registered global modules for verification
Restart your IIS server:
2.3 Add Module to a Specific Website Only (Alternative Method)
If you want to install the module for just one website, follow these steps:
Copy the correct DLL into a directory named
binunder your site’s root folder (e.g.,C:\inetpub\wwwroot\MySite\bin).Update the
web.configof that website:
Ensure the app pool identity has read access to this folder and its DLLs.
Restart your IIS server:
Step 3: Verify the Integration
Once installed:
Make a few requests to your IIS-hosted APIs.
In your Akto dashboard, go to the API Collections tab and confirm that traffic is appearing.
If no traffic is appearing, check:
IIS logs for module load errors.
Check logs in
C:\akto_configs\logs\log_20xx.txtAkto Data-Ingestion Service logs to ensure it’s receiving traffic.
Get Support for your Akto setup
There are multiple ways to request support from Akto. We are 24×7 available through the following:
In-app
Intercomsupport — message us via the chat icon in the Akto dashboard.Join our Discord channel for community support.
Email us at [email protected].
Visit our Contact page.
Last updated
Was this helpful?