Breadcrumbs

Correlation Fields for AWS

Connector Applicability

Applies to Source Connectors

AWS

Applies to Destination Connectors

All

Assumptions

These instructions assume you have already setup a source connection in CI Sync for AWS using the CI Sync instructions here: or Add AWS to SaaS Agent .

Pre-Read

Syncfish recommend customers read the following documentation before changing the Connection Setting/s described below.

  1. Understanding the use of CI Sync Connection Settings

  2. Rule 8 - Value used for Discovery Source Attribute for AWS

  3. Rule 9 - Correlation ID and Correlation Prefix Value for AWS

Locating and Amending the Connection Setting in the CI Sync UI

  1. Navigate to the Settings page

  2. Under the Source Connections heading (list), locate your AWS connection.

  3. Click the Update link on the right hand side of the AWS connection.

  4. Scroll down and locate the Section Heading and view the Individual Settings.

CleanShot 2025-08-15 at 14.59.51@2x-20250815-050033.png

The screen shot is provided only as sample to assist when reading this page. The state of your own CI Sync UI will depend on whether you are starting from the CI Sync default position or if you have already amended one/more of the settings.

  1. Tick the Override default box/boxes and then use the sliders related to the individual settings. The following table elaborates any further information about these particular settings.

Setting

Type

Additional Notes

Discovery Source

String

Can be changed to any string value that aligns to the customer specific requirements for this value in their ServiceNow.

The contents of this field is used as the value reference to sys_choice in ServiceNow (as distinct from the label of the sys_choice record).

Correlation ID Prefix

String

Any string value you want prefixed to the Correlation ID value CI Sync reads from AWS and persists against the CI in the CMDB.

  1. After modify the settings, scroll to the bottom of the page, tick the “I consent…” checkbox and finally click the Save connection button.

  2. You can now run a sync job and the amended settings will be applied causing the CI Sync Data Sync rules to be modified accordingly.

Importantly

Make sure you consciously override the setting against either your TEST or PROD environment (i.e. your TEST vs PROD sync jobs).

For more information on how to use TEST vs PROD Connection Settings please read Understanding the use of CI Sync Connection Settings.

Syncfish strongly recommend making changes for TEST environment/sync jobs first. Only modify PROD related settings after thoroughly validating the intended results in TEST.