RuleBasedMatchingResponse

The response of the Rule-based matching request.

AttributeTypesSelector

Configures information about the AttributeTypesSelector where the rule-based identity resolution uses to match profiles.

Required: No

ConflictResolution

How the auto-merging process should resolve conflicts between different profiles.

Required: No

Enabled

The flag that enables the rule-based matching process of duplicate profiles.

Type: Boolean

Required: No

ExportingConfig

Configuration information about the S3 bucket where Identity Resolution Jobs writes result files.

You need to give Customer Profiles service principal write permission to your S3 bucket. Otherwise, you'll get an exception in the API response. For an example policy, see Amazon Connect Customer Profiles cross-service confused deputy prevention.

Required: No

MatchingRules

Configures how the rule-based matching process should match profiles. You can have up to 15 MatchingRule in the MatchingRules.

Type: Array of MatchingRule objects

Array Members: Minimum number of 1 item. Maximum number of 15 items.

Required: No

MaxAllowedRuleLevelForMatching

Indicates the maximum allowed rule level.

Type: Integer

Valid Range: Minimum value of 1. Maximum value of 15.

Required: No

MaxAllowedRuleLevelForMerging

MatchingRule

Type: Integer

Valid Range: Minimum value of 1. Maximum value of 15.

Required: No

Status

PENDING

The first status after configuration a rule-based matching rule. If it is an existing domain, the rule-based Identity Resolution waits one hour before creating the matching rule. If it is a new domain, the system will skip the PENDING stage.

IN_PROGRESS

The system is creating the rule-based matching rule. Under this status, the system is evaluating the existing data and you can no longer change the Rule-based matching configuration.

ACTIVE

The rule is ready to use. You can change the rule a day after the status is in ACTIVE.

Type: String

Valid Values: PENDING | IN_PROGRESS | ACTIVE

Required: No

Contents