StartAudienceGenerationJobRequest
¶
Source code in docs_src/capo_cleanroomsml/types/start_audience_generation_job_request.py
collaboration_id
instance-attribute
¶
collaboration_id: NotRequired[UUID]
The identifier of the collaboration that contains the audience generation job.
configured_audience_model_arn
instance-attribute
¶
configured_audience_model_arn: ConfiguredAudienceModelArn
The Amazon Resource Name (ARN) of the configured audience model that is used for this audience generation job.
description
instance-attribute
¶
description: NotRequired[ResourceDescription]
The description of the audience generation job.
include_seed_in_output
instance-attribute
¶
include_seed_in_output: bool
Whether the seed audience is included in the audience generation output.
seed_audience
instance-attribute
¶
seed_audience: AudienceGenerationJobDataSource
The seed audience that is used to generate the audience.
tags
instance-attribute
¶
tags: NotRequired[TagMap]
The optional metadata that you apply to the resource to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define.
The following basic restrictions apply to tags:
-
Maximum number of tags per resource - 50.
-
For each resource, each tag key must be unique, and each tag key can have only one value.
-
Maximum key length - 128 Unicode characters in UTF-8.
-
Maximum value length - 256 Unicode characters in UTF-8.
-
If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.
-
Tag keys and values are case sensitive.
-
Do not use aws:, AWS:, or any upper or lowercase combination of such as a prefix for keys as it is reserved for AWS use. You cannot edit or delete tag keys with this prefix. Values can have this prefix. If a tag value has aws as its prefix but the key does not, then Clean Rooms ML considers it to be a user tag and will count against the limit of 50 tags. Tags with only the key prefix of aws do not count against your tags per resource limit.