Configure AES/AEMC integration properties

  • Release version: Australia
  • Updated May 7, 2026
  • 1 minute to read

    • Configure the AES/AEMC integration to enforce automated Scan Engine compliance checks on custom app deployment requests from App Engine Studio and ServiceNow Studio.

    Before you begin

    Important:
    Perform all steps in this task on the production controller instance only. Deployment pipelines within ServiceNow must already be configured before enabling this integration.
    Deployment pipelines must already be configured in ServiceNow. No OAuth credentials or My SN Instances authentication are required, only a single My SN Instances record designating the production controller.

    Role required: sn_se.scan_engine_admin

    Procedure

    Switch the default pipeline subflow
    1. Navigate to ALL > App Engine > Pipelines and Deployments > Pipeline Types.
    2. Open the default pipeline type record.
    3. Verify that Deployment Pipeline is set as the Application scope.
    4. Change Subflow to SE App Deployment Pipeline and save.
    Configure Scan Engine properties
    1. Navigate to ALL > Impact > Configuration > Scan Engine Properties > My SN Instances tab and select New.
    2. Create a single record with the following values:
      • Instance Name: Must match the instance_name system property
      • Instance URL
      • Environment: Production
      • Authentication Type: N/A (leave blank)
    3. Submit the form.
    4. Return to Scan Engine Properties and select the AES/AEMC Integration tab.
    5. Select Enable AES/AEMC Integration (Production Instance Only) to reveal additional configuration fields.
      If the checkbox does not appear, verify that the pipeline subflow was changed and the My SN Instances record was submitted correctly.
    6. Configure approval conditions and scan timeout.
      Setting Default
      Pass condition Scan score of 100
      Scan timeout 10 minutes