---
title: Starting and stopping ASE
description: For the API Security Engine (ASE) to start, the ase_master.key must be present in the /opt/pingidentity/ase/config directory.
component: pingintelligence
version: 5.2
page_id: pingintelligence:pingintelligence_reference_guide:pingintelligence_starting_and_stopping_ase
canonical_url: https://docs.pingidentity.com/pingintelligence/5.2/pingintelligence_reference_guide/pingintelligence_starting_and_stopping_ase.html
revdate: April 3, 2024
section_ids:
  before-you-begin: Before you begin
  about-this-task: About this task
  starting-ase: Starting ASE
  steps: Steps
  example: Example:
  stopping-ase: Stopping ASE
  steps-2: Steps
  example-2: Example:
---

# Starting and stopping ASE

## Before you begin

For the API Security Engine (ASE) to start, the `ase_master.key` must be present in the `/opt/pingidentity/ase/config` directory.

If you have moved the master key to a secured location for security reasons, copy it to the `/config` directory before executing the start script.

## About this task

|   |                                          |
| - | ---------------------------------------- |
|   | You can also run ASE as a non-root user. |

* Starting ASE

* Stopping ASE

## Starting ASE

### Steps

1. To check that the `nofile` limit in `/etc/security/limits.conf` is set to at least 65535 or higher on the host machine, run the following command on the ASE host machine:

   ```
   ulimit -n
   ```

2. Change the working directory to `bin` and run the `start.sh` script.

   #### Example:

   ```
   /opt/pingidentity/ase/bin/start.sh
   Starting API Security Enforcer 4.0.2...
   please see /opt/pingidentity/ase/logs/controller.log for more details
   ```

## Stopping ASE

### Steps

* Change working directory to `bin` and run the `stop.sh` script.

  #### Example:

  ```
  /opt/pingidentity/ase/bin/stop.sh -u admin –p admin
  checking API Security Enforcer status…sending stop request to ASE. please wait…
  API Security Enforcer stopped
  ```