# Map input data using an ID mapping workflow
An *ID mapping workflow* is a data processing job that maps data from an input data source to an input data target based on the specified ID mapping method. It produces an ID mapping table.
An ID mapping workflow requires an input data source and an input data target. Your data input source and target depends on the type of ID mapping that you want to perform. There are two ways to perform ID mapping: rule-based or provider services:
+ Rule-based ID mapping – You use matching rules to translate first-party data from a source to a target.
+ Provider services ID mapping – You use the LiveRamp provider service to translate third-party data from a source to a target.
**Note**
The provider services ID mapping workflow in AWS Entity Resolution is currently integrated with LiveRamp. If you have a subscription to the LiveRamp service, then you can create an ID mapping workflow with LiveRamp to perform transcoding. With LiveRamp transcoding, you can translate a set of source RampIDs into any target destination RampID. By using the RampID as a token to represent your customers, you can avoid sharing customer data directly with advertising platforms.
For more information, see [Perform Translation Through ADX](https://docs.liveramp.com/identity/en/perform-transcoding-through-adx.html) on the LiveRamp documentation website.
You can perform ID mapping between two datasets in either of the following scenarios:
+ Within your own AWS account
+ Across two different AWS accounts
The following diagram summarizes how to set up an ID mapping workflow.
![\[A summary of the four steps to create an ID mapping workflow in AWS Entity Resolution\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/HIW-ID-Mapping-Workflow.png)
**Topics**
+ [ID mapping workflow for one AWS account](creating-id-mapping-workflow-same-account.md)
+ [ID mapping workflow across two AWS accounts](creating-id-mapping-workflow-two-accounts.md)
+ [Running an ID mapping workflow](run-id-mapping-workflow.md)
+ [Running a custom ID mapping workflow](run-workflow-new-output-destination.md)
+ [Editing an ID mapping workflow](edit-id-mapping-workflow.md)
+ [Deleting an ID mapping workflow](delete-id-mapping-workflow.md)
+ [Adding or updating a resource policy for an ID mapping workflow](add-update-resource-policy-id-mapping.md)
# ID mapping workflow for one AWS account
An *ID mapping workflow for one AWS account* enables you to perform ID mapping between two datasets on your own AWS account.
Before you create an ID mapping workflow on your own AWS account, you must first complete the [prerequisites](id-mapping-workflow-prerequisite.md).
After you create and run an ID mapping workflow, you can view the output (the ID mapping table) and use it for analysis.
The following topics guide you through a set of steps to create an ID mapping workflow in the same AWS account.
**Topics**
+ [Prerequisites](id-mapping-workflow-prerequisite.md)
+ [Creating an ID mapping workflow (rule-based)](create-IDMW-rule-based-one-acct.md)
+ [Creating an ID mapping workflow (provider services)](create-IDMW-provider-services-one-acct.md)
# Prerequisites
Before you create an ID mapping workflow for one AWS account using either the **Rule-based** or the **Provider services** ID mapping method, you must first do the following:
+ Complete the tasks in [Setting up AWS Entity Resolution](https://docs.aws.amazon.com/entityresolution/latest/userguide/setting-up.html).
+ Complete the tasks in [Prepare input data tables](prepare-data-tables.md), depending on the type of input data you are using.
+ [Create a schema mapping](create-schema-mapping.md) or [Create a matching workflow](create-matching-workflow.md).
+ (**Provider services** ID mapping only) Before you create an ID mapping workflow with LiveRamp, you must choose an Amazon Simple Storage Service (Amazon S3) data staging bucket where you want to temporarily write the ID mapping workflow output.
If you are using the LiveRamp provider service to translate third-party data, add the following permissions policy, which allows you to access the data staging bucket.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::715724997226:root"
},
"Action": [
"s3:PutObject",
"s3:GetObject",
"s3:GetObjectVersion",
"s3:DeleteObject"
],
"Resource": [
"arn:aws:s3:::",
"arn:aws:s3:::/*"
]
},
{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::715724997226:root"
},
"Action": [
"s3:ListBucket",
"s3:GetBucketLocation",
"s3:GetBucketPolicy",
"s3:ListBucketVersions",
"s3:GetBucketAcl"
],
"Resource": [
"arn:aws:s3:::",
"arn:aws:s3:::/*"
]
}
]
}
```
------
In the preceding permissions policy, replace each ** with your own information.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/id-mapping-workflow-prerequisite.html)
# Creating an ID mapping workflow (rule-based)
This topic describes the process of creating an ID mapping workflow for one AWS account that uses matching rules to translate first-party data from a source to a target.
**To create a rule-based ID mapping workflow for one AWS account**
1. Sign in to the AWS Management Console and open the AWS Entity Resolution console at [https://console.aws.amazon.com/entityresolution/](https://console.aws.amazon.com/entityresolution/).
1. In the left navigation pane, under **Workflows**, choose **ID mapping**.
1. On the **ID mapping workflows** page, in the upper right corner, choose **Create ID mapping workflow**.
1. For **Step 1: Specify ID mapping workflow details**, do the following.
1. Enter an **ID mapping workflow name** and an optional **Description**.
![\[The name and description fields on the Specify ID mapping workflow page\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/specify-ID-mapping-details-name.png)
1. For the **ID mapping method**, choose **Rule-based**.
1. (Optional) To process only new, updated, or deleted records in the workflow, select **Enable incremental processing**.
![\[The ID mapping section of the Specify ID mapping workflow page with the Enable incremental process checkbox selected.\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/id-mapping-method-enable-inc-proc.png)
AWS Entity Resolution processes only new, updated, or deleted records in either the Source or Target ID namespace, rather than recreating the entire ID mapping table.
When you choose incremental processing and your data table has a DELETE column, AWS Entity Resolution handles records differently based on the DELETE column value.
+ Records marked as `true` in the DELETE column are removed from the ID mapping table.
+ Records marked as `false` in the DELETE column are ingested into Amazon S3.
If you leave this option unselected, AWS Entity Resolution runs the default batch processing ID mapping workflow on the ID mapping table.
1. (Optional) To enable **Tags** for the resource, choose **Add new tag**, and then enter the **Key** and **Value** pair.
1. Choose **Next**.
1. For **Step 2: Specify source and target**, do the following.
1. For **Source**, choose the scenario that applies to you and then take the recommended action.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/create-IDMW-rule-based-one-acct.html)
1. For **Target**, select an existing **Matching workflow** from the dropdown list.
1. For **Rule parameters**, do the following.
1. Specify the **Rule controls** by choosing one of the following options based on your source type.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/create-IDMW-rule-based-one-acct.html)
1. For **Comparison and matching parameters**, the **Comparison type** is automatically set to **Multiple input fields**.
This is because both participants had selected this option previously.
1. Specify the **Record matching type** by choosing one of the following options based on your goal.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/create-IDMW-rule-based-one-acct.html)
**Note**
You must specify compatible limitations for the source and target ID namespaces.
1. To specify the **Service access** permissions, choose an option and take the recommended action.
![\[The Service access options on the Specify source and target page\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/specify-source-target-service-access.PNG)
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/create-IDMW-rule-based-one-acct.html)
1. Choose **Next**.
1. For **Step 3: Specify data output location – *optional***, do the following.
1. For **Data output destination**, do the following:
1. Choose the **Amazon S3 location** for the data output.
1. For **Encryption**, if you choose to **Customize encryption settings**, then enter the **AWS KMS key** ARN or choose **Create an AWS KMS key**.
1. Choose **Next**.
1. For **Step 4: Review and create**, do the following.
1. Review the selections that you made for the previous steps and edit them if necessary.
1. Choose **Create**.
A message appears, indicating that the ID mapping workflow has been created.
After you create the ID mapping workflow, you're ready to [run an ID mapping workflow](run-id-mapping-workflow.md).
# Creating an ID mapping workflow (provider services)
This topic describes the process of creating an ID mapping workflow for one AWS account using a provider service called LiveRamp. LiveRamp translates a set of source RampIDs to another set using either maintained or derived RampIDs.
**To create a provider service-based ID mapping workflow for one AWS account**
1. Sign in to the AWS Management Console and open the AWS Entity Resolution console at [https://console.aws.amazon.com/entityresolution/](https://console.aws.amazon.com/entityresolution/).
1. In the left navigation pane, under **Workflows**, choose **ID mapping**.
1. On the **ID mapping workflows** page, in the upper right corner, choose **Create ID mapping workflow**.
1. For **Step 1: Specify ID mapping workflow details**, do the following.
1. Enter an **ID mapping workflow name** and an optional **Description**.
![\[The name and description fields on the Specify ID mapping workflow page\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/specify-ID-mapping-details-name.png)
1. For the **ID mapping method**, choose **Provider services**.
AWS Entity Resolution currently offers the LiveRamp provider service as an ID mapping method. If you have a subscription to LiveRamp, then the status appears as **Subscribed**. For more information about how to subscribe to LiveRamp, see [Step 1: Subscribe to a provider service on AWS Data Exchange](prepare-third-party-input-data.md#subscribe-provider-service).
![\[The Subscribed status for the LiveRamp ID mapping method on the Specify ID mapping workflow page\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/id-mapping-method.PNG)
**Note**
Ensure that your data input file format aligns with the provider service's guidelines. For more information about LiveRamp's input file formatting guidelines, see [Perform Translation Through ADX](https://docs.liveramp.com/identity/en/perform-transcoding-through-adx.html) on the LiveRamp documentation website.
1. For **LiveRamp configuration**, enter the following values that LiveRamp provides:
+ **Client ID manager ARN**
+ **Client secret manager ARN**
![\[The LiveRamp configuration fields on the Specify ID mapping workflow page\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/liveramp-configuration.PNG)
1. (Optional) To enable **Tags** for the resource, choose **Add new tag**, and then enter the **Key** and **Value** pair.
1. Choose **Next**.
1. For **Step 2: Specify source and target**, do the following.
1. For **Source**, choose the scenario that applies to you and then take the recommended action.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/create-IDMW-provider-services-one-acct.html)
1. For **Target**, take one of the following actions based on your chosen ID mapping method.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/create-IDMW-provider-services-one-acct.html)
1. For **Data staging**, choose the **Amazon S3 location** where you want to temporarily write the ID mapping workflow output.
![\[The Data staging field on the Specify source and target page\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/data-staging.PNG)
1. To specify the **Service access** permissions, choose an option and take the recommended action.
![\[The Service access options on the Specify source and target page\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/specify-source-target-service-access.PNG)
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/create-IDMW-provider-services-one-acct.html)
1. Choose **Next**.
1. For **Step 3: Specify data output location – *optional***, do the following.
1. For **Data output destination**, do the following:
1. Choose the **Amazon S3 location** for the data output.
1. For **Encryption**, if you choose to **Customize encryption settings**, then enter the **AWS KMS key** ARN or choose **Create an AWS KMS key**.
1. View the **LiveRamp generated output**.
1. Choose **Next**.
![\[The Data output destination fields on the Specify data output location page\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/specify-data-ouput-IDM.PNG)
1. For **Step 4: Review and create**, do the following.
1. Review the selections that you made for the previous steps and edit them if necessary.
1. Choose **Create**.
A message appears, indicating that the ID mapping workflow has been created.
1. After you create the ID mapping workflow, you're ready to [run an ID mapping workflow](run-id-mapping-workflow.md).
# ID mapping workflow across two AWS accounts
An *ID mapping workflow across two AWS accounts* enables you to perform ID mapping between two datasets across two AWS accounts. This is typically done between your own AWS account and another AWS account.
For example, a publisher can create an ID mapping workflow using their own target ID namespace (in their own AWS account) and an advertiser’s source ID namespace (in another AWS account).
Before you create an ID mapping workflow across two AWS accounts, you must first complete the [prerequisites](create-idmw-two-accounts-prerequisite.md).
After you create an ID mapping workflow, you can view the output (the ID mapping table) and use it for analysis.
The following topics guide you through a set of steps to create an ID mapping workflow across two AWS accounts:
**Topics**
+ [Prerequisites](create-idmw-two-accounts-prerequisite.md)
+ [Creating an ID mapping workflow (rule-based)](create-id-mapping-workflow-procedure.md)
+ [Creating an ID mapping workflow (provider services)](create-id-mapping-workflow-provider-services.md)
# Prerequisites
Before you create an ID mapping workflow across two AWS accounts, you must first do the following:
+ Complete the tasks in [Set up AWS Entity Resolution](setting-up.md).
+ [Create an ID namespace source](create-id-namespace-source.md).
+ [Create an ID namespace target](create-id-namespace-target.md).
+ Acquire the ID namespace ARN if you are using an ID namespace source from another AWS account.
+ (**Provider services** only) Creating an ID mapping workflow across two AWS accounts requires permission for LiveRamp to access the S3 bucket and the AWS Key Management Service (AWS KMS) customer managed key.
Before you create an ID mapping workflow across two AWS accounts with LiveRamp, add the following permission policy, which allows LiveRamp to access the S3 bucket and the customer managed key.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::715724997226:root"
},
"Action": [
"kms:Decrypt"
],
"Resource": "arn:aws:kms:us-east-1:111122223333:key/key-id",
"Condition": {
"StringEquals": {
"kms:ViaService": "s3.us-east-1.amazonaws.com"
}
}
}]
}
```
------
In the preceding permissions policy, replace each ** with your own information.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/create-idmw-two-accounts-prerequisite.html)
# Creating an ID mapping workflow (rule-based)
After you've completed the [prerequisites](create-idmw-two-accounts-prerequisite.md), you can create one or more ID mapping workflows to use matching rules to translate first-party data from a source to a target.
**To create a rule-based ID mapping workflow across two AWS accounts**
1. Sign in to the AWS Management Console and open the AWS Entity Resolution console at [https://console.aws.amazon.com/entityresolution/](https://console.aws.amazon.com/entityresolution/).
1. In the left navigation pane, under **Workflows**, choose **ID mapping**.
1. On the **ID mapping workflows** page, in the upper right corner, choose **Create ID mapping workflow**.
1. For **Step 1: Specify ID mapping workflow details**, do the following.
1. Enter an **ID mapping workflow name** and an optional **Description**.
![\[The Name and Description fields on the Specify ID mapping workflow details page\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/specify-ID-mapping-details-name.png)
1. For the **ID mapping method**, choose **Rule-based**.
1. (Optional) To process only new, updated, or deleted records in the workflow, select **Enable incremental processing**.
![\[The ID mapping section of the Specify ID mapping workflow page with the Enable incremental process checkbox selected.\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/id-mapping-method-enable-inc-proc.png)
AWS Entity Resolution processes only new, updated, or deleted records in either the Source or Target ID namespace, rather than recreating the entire ID mapping table.
When you choose incremental processing and your data table has a DELETE column, AWS Entity Resolution handles records differently based on the DELETE column value.
+ Records marked as `true` in the DELETE column are removed from the ID mapping table.
+ Records marked as `false` in the DELETE column are ingested into Amazon S3.
If you leave this option unselected, AWS Entity Resolution runs the default batch processing ID mapping workflow on the ID mapping table.
1. (Optional) To enable **Tags** for the resource, choose **Add new tag**, and then enter the **Key** and **Value** pair.
1. Choose **Next**.
1. For **Step 2: Specify source and target**, do the following.
1. Turn on **Advanced options**.
1. For **Source**, choose **Matching workflow**, and then select the existing **Matching workflow** from the dropdown list.
1. For **Target**, choose **Matching workflow**, and then select the existing **Matching workflow** from the dropdown list.
1. For **Rule parameters**, specify the **Rule controls** by choosing whether a **Source** or a **Target** can provide rules in an ID mapping workflow.
Rule controls must be compatible between the source and the target to be used in an ID mapping workflow. For example, if a source ID namespace limits rules to the target but the target ID namespace limits rules to the source, this results in an error.
1. For **Comparison and matching parameters**, do the following.
1. Specify the **Comparison type** by choosing an option based on your goal.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/create-id-mapping-workflow-procedure.html)
1. Specify the **Record matching type** by choosing an option based on your goal.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/create-id-mapping-workflow-procedure.html)
**Note**
You must specify compatible limitations for the source and target ID namespaces.
1. To specify the **Service access** permissions, choose an option and take the recommended action.
![\[The Service access options on the Specify source and target page\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/specify-source-target-service-access.PNG)
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/create-id-mapping-workflow-procedure.html)
1. Choose **Next**.
1. For **Step 3: Specify data output location – *optional***, do the following.
1. For **Data output destination**, do the following.
1. Choose the **Amazon S3 location** for the data output.
1. For **Encryption**, if you choose to **Customize encryption settings**, then enter the **AWS KMS key** ARN or choose **Create an AWS KMS key**.
1. View the **LiveRamp generated output**.
1. Choose **Next**.
1. For **Step 4: Review and create**, do the following.
1. Review the selections that you made for the previous steps and edit them if necessary.
1. Choose **Create**.
A message appears, indicating that the ID mapping workflow has been created.
After you create the ID mapping workflow, you're ready to [run an ID mapping workflow](run-id-mapping-workflow.md).
# Creating an ID mapping workflow (provider services)
After completing the [prerequisites](create-idmw-two-accounts-prerequisite.md), you can create one or more ID mapping workflows using the LiveRamp provider service. LiveRamp translates a set of source RampIDs to another set using either maintained or derived RampIDs.
**To create an ID mapping workflow using the provider service**
1. Sign in to the AWS Management Console and open the AWS Entity Resolution console at [https://console.aws.amazon.com/entityresolution/](https://console.aws.amazon.com/entityresolution/).
1. In the left navigation pane, under **Workflows**, choose **ID mapping**.
1. On the **ID mapping workflows** page, in the upper right corner, choose **Create ID mapping workflow**.
1. For **Step 1: Specify ID mapping workflow details**, do the following.
1. Enter an **ID mapping workflow name** and an optional **Description**.
![\[The Name and Description fields on the Specify ID mapping workflow details page\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/specify-ID-mapping-details-name.png)
1. For the **ID mapping method**, choose **Provider services**.
AWS Entity Resolution currently offers the LiveRamp provider service as an ID mapping method. If you have a subscription to LiveRamp, then the status appears as **Subscribed**. For more information about how to subscribe to LiveRamp, see [Step 1: Subscribe to a provider service on AWS Data Exchange](prepare-third-party-input-data.md#subscribe-provider-service).
![\[The Subscribed status for the LiveRamp ID mapping method on the Specify ID mapping workflow page\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/id-mapping-method.PNG)
**Note**
Ensure that your data input file format aligns with the provider service's guidelines. For more information about LiveRamp's input file formatting guidelines, see [Perform Translation Through ADX](https://docs.liveramp.com/identity/en/perform-transcoding-through-adx.html) on the LiveRamp documentation website.
1. For **LiveRamp configuration**, enter the following values that LiveRamp provides:
+ **Client ID manager ARN**
+ **Client secret manager ARN**
![\[The LiveRamp configuration fields on the Specify ID mapping workflow page\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/liveramp-configuration.PNG)
1. (Optional) To enable **Tags** for the resource, choose **Add new tag**, and then enter the **Key** and **Value** pair.
1. Choose **Next**.
1. For **Step 2: Specify source and target**, do the following.
1. Turn on **Advanced options**.
1. For **Source**, choose **ID namespace**.
![\[The Source fields on the Specify source and target page\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/specify-source-id-namespace.PNG)
1. For ID namespace, identify where the ID namespace is located, and then take the recommended action.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/create-id-mapping-workflow-provider-services.html)
1. For **Target**, choose **ID namespace**.
![\[The Target field on the Specify source and target page\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/specify-target-id-namespace.PNG)
1. To specify the **Service access** permissions, choose an option and take the recommended action.
![\[The Service access options on the Specify source and target page\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/specify-source-target-service-access.PNG)
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/create-id-mapping-workflow-provider-services.html)
1. Choose **Next**.
1. For **Step 3: Specify data output location – *optional***, do the following.
1. For **Data output destination**, do the following.
1. Choose the **Amazon S3 location** for the data output.
1. For **Encryption**, if you choose to **Customize encryption settings**, then enter the **AWS KMS key** ARN or choose **Create an AWS KMS key**.
1. View the **LiveRamp generated output**.
1. Choose **Next**.
![\[The Data output destination fields on the Specify data output location page\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/images/specify-data-ouput-IDM.PNG)
1. For **Step 4: Review and create**, do the following.
1. Review the selections that you made for the previous steps and edit them if necessary.
1. Choose **Create**.
A message appears, indicating that the ID mapping workflow has been created.
After you create the ID mapping workflow, you're ready to [run an ID mapping workflow](run-id-mapping-workflow.md).
# Running an ID mapping workflow
After you [create an ID mapping workflow for one AWS account](creating-id-mapping-workflow-same-account.md) or [create an ID mapping workflow across two AWS accounts](creating-id-mapping-workflow-two-accounts.md), you can run the ID mapping workflow. The ID mapping workflow outputs a CSV file.
**To run an ID mapping workflow**
1. Sign in to the AWS Management Console and open the AWS Entity Resolution console at [https://console.aws.amazon.com/entityresolution/](https://console.aws.amazon.com/entityresolution/).
1. In the left navigation pane, under **Workflows**, choose **ID mapping**.
1. Choose the ID mapping workflow.
1. On the ID mapping workflow details page, in the upper right corner, choose **Run**.
1. On the matching workflow details page, on the **Metrics** tab, view the following under **Last job metrics**:
+ The **Job ID**
+ The **Status** of the matching workflow job: **Queued**, **In progress**, **Completed**, **Failed**
+ The **Run type**
+ The **Time started** for the workflow job
+ The **Time completed** for the workflow job
+ The **Duration** of the workflow job
+ The **Output destination**
+ The **AWS KMS key**
+ The **Service role**
+ The number of **Input records**
+ The number of **Unique records**
+ The number of **New unique records loaded**
+ The number of **Mapped records**
+ The number of **Mapped records removed**
+ The number of **New mapped records**
+ The number of **Mapped source records**
+ The number of **New mapped source records **
+ The number of **Mapped source records removed**
+ The number of **Mapped target records**
+ The number of **New mapped target records**
+ The number of **Mapped target records removed**
+ The number of **Delete records processed**
+ The number of **Records processed**
+ The number of **Records not processed**
Under **Job history**, you can also view the job metrics for previously run ID mapping workflow jobs.
1. After the ID mapping workflow job completes (status is **Completed**), choose **Data output**, and then choose your **Amazon S3 location** to view the results.
After you get your CSV file, you can join the `RAMPID` with the `TRANSCODED_ID`.
# Running a custom ID mapping workflow
**Note**
This procedure is available for [workflows within a single AWS account](creating-id-mapping-workflow-same-account.md) or [workflows that span two AWS accounts](creating-id-mapping-workflow-two-accounts.md) with incremental processing enabled.
When running an ID mapping workflow, you can specify a different Amazon S3 location for your output data than what was originally configured. You can also choose how to process your data by selecting one of three run types: **Batch** (processes all data), **Incremental** (processes only new or changed data), or **Delete only** (processes only deletion requests).
**To run an ID mapping workflow with a new output destination**
1. Sign in to the AWS Management Console and open the AWS Entity Resolution console at [https://console.aws.amazon.com/entityresolution/](https://console.aws.amazon.com/entityresolution/).
1. In the left navigation pane, under **Workflows**, choose **ID mapping**.
1. Choose the ID mapping workflow that you want to run.
1. On the ID mapping workflow details page, choose **Run workflow**, and then choose **Run with new output destination**.
1. For **Data output destination**, configure the following.
1. For **Run type**, select one of the following options.
+ **Batch** – Processes the entire ID mapping table.
Recommended for initial setup, periodic full refreshes, or when significant changes occur in both Source and Target ID namespaces.
+ **Incremental** – Processes only new, updated, or deleted records in either the Source or Target ID namespace.
Recommended for frequent updates, daily runs, or real-time data synchronization.
+ **Delete only** – Processes only deleted records from the Target ID namespace.
Recommended for quickly synchronizing removals.
1. Choose the **Amazon S3 location** for the data output.
1. For **Encryption**, do one of the following:
+ Keep the default encryption settings
+ Choose **Customize encryption settings**, and either enter the **AWS KMS key** ARN or choose **Create an AWS KMS key**.
1. To specify the **Service access** permissions, choose an option and take the recommended action.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/entityresolution/latest/userguide/run-workflow-new-output-destination.html)
1. Choose **Run**.
1. On the matching workflow details page, on the **Metrics** tab, view the following under **Last job metrics**:
+ The **Job ID**
+ The **Time completed** for the workflow job
+ The **Status** of the matching workflow job: **Queued**, **In progress**, **Completed**, **Failed**
+ The number of **Records processed**
+ The number of **Records not processed**
+ The number of **Input records**
+ The number of **Unique match IDs generated**.
+ The number of **New mapped records**.
+ The number of **New mapped target records**.
+ The number of **New mapped source records**.
+ The number of **New mapped source records removed**.
+ The number of **New mapped target records removed**.
+ The number of **New mapped records removed**.
Under **Job history**, you can also view the job metrics for previously run ID mapping workflow jobs.
1. After the ID mapping workflow job completes (status is **Completed**), choose **Data output**, and then choose your **Amazon S3 location** to view the results.
After you get your CSV file, you can join the `RAMPID` with the `TRANSCODED_ID`.
# Editing an ID mapping workflow
Editing the ID mapping workflow allows you to keep your entity resolution capabilities up-to-date and aligned with your evolving business needs over time. You may want to adjust the mapping rules, techniques, and parameters, you can optimize the workflow to provide more accurate and reliable ID matching results. You may also want to add new data sources, expand the types of IDs being mapped, or incorporate additional matching criteria into the workflow. If you identify problems or errors in ID mapping results, editing with workflow can help you diagnose and resolve those issues.
**To edit an ID mapping workflow:**
1. Sign in to the AWS Management Console and open the AWS Entity Resolution console at [https://console.aws.amazon.com/entityresolution/](https://console.aws.amazon.com/entityresolution/).
1. In the left navigation pane, under **Workflows**, choose **ID mapping**.
1. Choose the ID mapping workflow.
1. On the ID mapping workflow details page, in the upper right corner, choose **Edit**.
1. On the **Specify ID mapping workflow details** page, make any necessary changes and then choose **Next**.
1. On the **Specify data output** page, make any necessary changes and then choose **Next**.
1. On the **Review and save** page, make any necessary changes and then choose **Save**.
# Deleting an ID mapping workflow
If you no longer use an ID mapping workflow, deleting it can help streamline your workflow management. In addition, deleting redundant or less efficient ID mapping workflows that serve similar purposes can help you consolidate your processes.
**To delete an ID mapping workflow:**
1. Sign in to the AWS Management Console and open the AWS Entity Resolution console at [https://console.aws.amazon.com/entityresolution/](https://console.aws.amazon.com/entityresolution/).
1. In the left navigation pane, under **Workflows**, choose **ID mapping**.
1. Choose the ID mapping workflow.
1. On the ID mapping workflow details page, in the upper right corner, choose **Delete**.
1. Confirm the deletion and then choose **Delete**.
# Adding or updating a resource policy for an ID mapping workflow
A resource policy allows the creator of the ID mapping resource to access your ID mapping workflow resource.
**To add or update a resource policy**
1. Sign in to the AWS Management Console and open the AWS Entity Resolution console at [https://console.aws.amazon.com/entityresolution/](https://console.aws.amazon.com/entityresolution/).
1. In the left navigation pane, under **Workflows**, choose **ID mapping**.
1. Choose the ID mapping workflow.
1. On the ID mapping workflow details page, choose the **Permissions** tab.
1. In the **Resource policy**, section choose **Edit**.
1. Add or update the policy in the JSON editor.
1. Choose **Save changes**.