---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia 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}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

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

## Vorbereitungen

* 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/3IDBT71oapHdBE_T6JFg8A#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

## Warum und wann dieser Vorgang ausgeführt wird

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.

## Prozedur

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.