---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Retire legacy AWS API Gateway data model CIs

# Retire legacy AWS API Gateway data model CIs {#ariaid-title1}

* Release version: Yokohama
* 
* Updated October 28, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Avoid duplicate AWS API Gateway configuration items (CIs) by retiring legacy data model CIs through a scheduled job.

## Before you begin

* Verify you have at least version 1.29.0 of Discovery and Service Mapping Patterns.
* Run an AWS discovery to populate the CIs in the managed API data model. For more information, see [Create discovery schedules for cloud resources](https://servicenow-prod.fluidtopics.net/mvUB4lhtHGGrh93mggIcpw#discovery-manager "Create schedules for discovering cloud resources based on the cloud discovery method you choose; that is, service accounts or IP ranges.").
{#retire-legacy-aws-api-gateway-cis__ul_lv4_ppw_chc}

Role required: admin

## About this task

Starting with Discovery and Service Mapping Patterns December release, the Amazon AWS API Gateway pattern data model has changed. To avoid duplicate CIs, activate a schedule job to mark legacy data model CIs as retired.

## Procedure

1. Navigate to AllSystem DefinitionScheduled Jobs.
2. In the Name column, search for <kbd class="ph userinput">Retire Cloud Gateways migrated to Managed API</kbd>.
3. Select the Retire Cloud Gateways migrated to Managed API scheduled job.
4. Select Execute Now.

*[\>]: and then