Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

CreateDomainRequest

import type { CreateDomainRequest } from "https://aws-api.deno.dev/v0.4/services/customerprofiles.ts?docs=full";
interface CreateDomainRequest {
DeadLetterQueueUrl?: string | null;
DefaultEncryptionKey?: string | null;
DefaultExpirationDays: number;
DomainName: string;
Matching?: MatchingRequest | null;
Tags?: {
[key: string]: string | null | undefined;
}
| null;
}

§Properties

§
DeadLetterQueueUrl?: string | null
[src]

The URL of the SQS dead letter queue, which is used for reporting errors associated with ingesting data from third party applications. You must set up a policy on the DeadLetterQueue for the SendMessage operation to enable Amazon Connect Customer Profiles to send messages to the DeadLetterQueue.

§
DefaultEncryptionKey?: string | null
[src]

The default encryption key, which is an AWS managed key, is used when no specific type of encryption key is specified. It is used to encrypt all data before it is placed in permanent or semi-permanent storage.

§
DefaultExpirationDays: number
[src]

The default number of days until the data within the domain expires.

§
DomainName: string
[src]

The unique name of the domain.

§
Matching?: MatchingRequest | null
[src]

The process of matching duplicate profiles. If Matching = true, Amazon Connect Customer Profiles starts a weekly batch process called Identity Resolution Job. If you do not specify a date and time for Identity Resolution Job to run, by default it runs every Saturday at 12AM UTC to detect duplicate profiles in your domains.

After the Identity Resolution Job completes, use the GetMatches API to return and review the results. Or, if you have configured ExportingConfig in the MatchingRequest, you can download the results from S3.

§
Tags?: {
[key: string]: string | null | undefined;
}
| null
[src]

The tags used to organize, track, or control access for this resource.