Tag Synchronization for Assigned To in 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: 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. FAQ - Overview of Cloud Tag, Cloud Label and VMware Custom Attribute Synchronization Capabilities of CI Sync

  3. Rule 10 - AWS Tag Synchronization

  4. Rule 14 - Synchronization of User Oriented Tag from 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.

azure assigned to 2.jpg

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

Enable for Assigned To

Slider

If enabled, defined Tags will be synchronized to the assigned_to field against CIs in the CMDB.

When enabled, the Assigned To Tag RegEx field will be exposed (see below).

For a diagrammatic view of how Assigned To user synchronization works in CI Sync (covering both the source system behaviour/settings and the destination system behaviour settings), please read the Addition Information section on this AWS Default Config Guide page:

Rule 14 - Synchronization of User Oriented Tag from AWS

Important PII Consideration when enabling this setting

When enabling this setting the CI Sync UI will warn of potential PII implications. Please read the message shown and also read Section 7 (Overview of data used within the Service) in the CI Sync Service Specification published here. Section 7 explains the impact of enabling this setting for both persisted data and transited data.

Assigned To Tag RegEx

RegEx

Enter a Regular Expression that matches one or more Tag names in AWS (i.e. one or more Tags that represent the Assigned To associated with the AWS resource).

Example RegEx

/^Assignee$|^AssigneeTag$|^AssignedTo 1$|^AssignedTo 2$|^AssignedTo1$|^AssignedTo2$/

RegEx Explained

This RegEx will identify Labels (or Tags) named “Assignee”, “AssigneeTag”, “AssignedTo 1”, “AssignedTo 2”, “AssignedTo1” or “AssignedTo2” (i.e. six variations) and sync’d the associated values into ServiceNow.

Sync Behaviour and ServiceNow Data Explained

  1. If there are multiple Tags that match the defined regEx for a field, the value within each Tag will be searched against the ServiceNow sys_user table. The CI Sync lookup ranks the results to return active users first.

  2. If there are multiple values within a Tag (including multiple Tags), either comma or semi-colon separated, the individual values will be extracted and searched individually against the ServiceNow sys_user table with the first matching value returned.

  3. Once a match is returned, CI Sync will store the matching sys_user value against the assigned_to field on the CI. If not match is found, the assigned_to attribute on the CI will be blank.

  4. Regardless of whether a match is found (or not), CI Sync will also populate the ServiceNow cmdb_key_value table with the raw label (tag) data (i.e. an entry will be created in cmdb_key_value for each Tag and it’s raw value).

Syncfish recommend customers read the following FAQ for more information about the behaviour of Tag (or Label) synchronization into ServiceNow.

FAQ - Overview of Cloud Tag, Cloud Label and VMware Custom Attribute Synchronization Capabilities of CI Sync

Assigned to Value Replacements

Choicelist

For context in AWS: AWS is restrictive as to the values allowed in Tags, therefore CI Sync provides support for transforming AWS Tags into valid user names. For user names: as AWS does not allow for the entry of space characters in Label values, CI Sync provides for the substitution of either “-” or “_” with a space character when searching the sys_user.name field.

This setting allows customers to define a search and replace RegEx express that acts on the values read from a given Tag.

Enter a Regular Expression that defines the search string and the replacement value string.

The RegEx format consists of a two element array. The first element is the search RegEx and the second element is the replacement text.

Example RegEx

[['/dot/', '.'],['/at/', '@']]

RegEx Explained

This RegEx will replace the literal text “dot” with a “.” (period) character, and will replace the literal text “at” with the “@” symbol. For example “AndrewdotKentatsyncfishdotcomdotau” will be transformed to “Andrew.Kent@syncfish.com.au” (without the quotes.. they are just for reference in this documentation)

Assigned to Lookups

Choicelist

Select one of the available choicelist items which control sys_user attribute/s CI Sync searches using the value/s in the tag.

See below for the available choices.

CleanShot 2025-09-16 at 15.24.07@2x-20250916-052411.png

In this example if you select ‘e-mail [email] & Name [name]' you will see a message as per below explaining that you must select the corresponding options in the ServiceNow destination connection 'User Synchronization’ section. Please refer to the document linked below.

Define a User oriented attribute when using User Synchronization from a Source System in ServiceNow

If the corresponding selection in ServiceNow is not made the sync job will error.

image-20260814-052540.png
  1. After modifying 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.