---
title: Inline ASE
description: In the inline deployment mode, API Security Enforcer (ASE) sits at the edge of your network to receive the application programming interface (API) traffic.
component: pingintelligence
version: 5.2
page_id: pingintelligence:pingintelligence_reference_guide:pingintelligence_inline_ase
canonical_url: https://docs.pingidentity.com/pingintelligence/5.2/pingintelligence_reference_guide/pingintelligence_inline_ase.html
revdate: April 3, 2024
---

# Inline ASE

In the inline deployment mode, API Security Enforcer (ASE) sits at the edge of your network to receive the application programming interface (API) *(tooltip: \<div class="paragraph">
\<p>A specification of interactions available for building software to access an application or service.\</p>
\</div>)* traffic.

ASE can be deployed behind an existing load balancer such as Amazon Web Service (AWS) ELB. ASE deployed at the edge of the data center terminates SSL connections from API clients. It then routes the requests directly to the correct destination APIs and app servers such as Node.js, WebLogic, Tomcat, PHP, etc.

![ASE in inline deployment mode](../_images/wst1564009022393.png)

To configure ASE to work in Inline mode, set the `mode=inline` in the `ase.conf` file.

Some load balancers (for example, Amazon Web Services (AWS) *(tooltip: \<div class="paragraph">
\<p>An Amazon subsidiary providing cloud computing platforms.\</p>
\</div>)* ELB) require responses to keep alive messages from all devices receiving traffic. In an inline mode configuration, ASE should be configured to respond to these keep alive messages by updating the `ase_health` variable in the `ase.conf` file. When `ase_health` is set to `true`, load balancers can perform an ASE health check using the following URL: `http(s)://<ASE Name>/ase`, where *\<ASE Name>* is the ASE domain name. ASE will respond to these health checks.