---
sourceDocument: Australia Impact
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/impact

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Deployment and synchronization integrations

# Deployment and synchronization integrations {#ariaid-title1}

* Release version: Australia
* 
* Updated May 7, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

The AES/AEMC and Update set integrations control how custom app deployments are
governed and how scan results are synchronized across your instance stack.

Unlike the Definitions, Exception Reason, and User Story integrations, which act on individual findings or definitions,these integrations operate at the instance level, enforcing governance across deployment pipelines and keeping
scan data consistent between developer and production instances.

## AES/AEMC integration

The AES/AEMC integration intercepts custom app deployment requests submitted from App Engine Studio or ServiceNow Studio and runs a Scan EngineScan Engine compliance check before allowing the request to advance. Deployments that do not meet the configured conditions are rejected and the application author receives an email with scan
details.

This integration is configured on the production controller instance only. Deployment pipelines must already be configured in ServiceNow production instances before enabling it. No OAuth credentials or My SN Instances authentication are required beyond a single My SN Instances record designating the production controller.  
Important:  
The pass condition defaults to a scan score of 100 and the scan timeout defaults to 10 minutes. Both values are configurable.

## Update set integration

The Update set integration automatically synchronizes update set scan results from
developer instances to all Production instances registered in My SN Instances when a scan
is marked complete. Optionally, enable summary scan synchronization to keep update set
summaries in sync across instances.  
Note:  
The Update set integration requires the `admin` role, not the Scan Engine-specific roles used by other integrations. My SN Instances registration and authentication must be complete before configuring this integration. See [Register your instance](https://servicenow-prod.fluidtopics.net/CW_9LTbn1YISzXh4d4sYSg "Register each participating ServiceNow instance in the My SN Instances table before configuring any instance-to-instance integration.").
* **[Configure AES/AEMC integration properties](https://servicenow-prod.fluidtopics.net/WZu0H1C3F4pMCK0aB1iA3w)**   
  Configure the AES/AEMC integration to enforce automated Scan Engine compliance checks on custom app deployment requests from App Engine Studio and ServiceNow Studio.
* **[Configure update set integration](https://servicenow-prod.fluidtopics.net/o8SuexD1W4_OeqVX3HDTFA)**   
  Configure the update set integration to automatically synchronize update set scan results from developer instances to the production instance.