Amazon Personalize

awsAI serviceaws-personalize

Managed recommendation service serving personalized items from your interaction data.

Provider
aws
Category
Compute
Properties · 5 set by this component
propertytypevaluesrequiredkind defaultthis component
authenumapi-key | oauth | iam | noneno—▸ iam
campaignsPerDatasetGroup · component propertyinteger—no5inherited
contentFilteringboolean—no—inherited
customerManagedKeysboolean—no—▸ false
dataResidency · advancedenumus | eu | asia | globalno—inherited
dataRetentionDaysinteger—no—inherited
keyStoreboolean—nofalseinherited
managedboolean—nofalse▸ true
modalityenumtext | vision | speech | multimodal | structured | image | video | audio | embedding | rerankno—▸ structured
publicEndpointboolean—no—▸ true
putEventsPerSecond · component propertyinteger—no1000inherited
quotaUnitsPerMinuteinteger—no—inherited
rateLimitRpm · advancedinteger—no—inherited
rateLimitTpm · advancedinteger—no—inherited
realTimeEventIngestion · component propertyboolean—nofalseinherited
requestsPerSecondPerCampaign · component propertyinteger—no500inherited
servingMode · component propertyenumcampaign | recommender | batch-inferencenocampaigninherited
viaGatewayboolean—nofalseinherited
Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

ai-api-key-unmanaged

This AI vendor is reached with an API key, and nothing in the design holds or rotates that key. It ends up in environment files or code, every caller shares it, and a single leak runs up the vendor bill until someone notices. Put the key in a key-management component, or say it is held there with keyStore.

  • — all of these hold:
  • — the node's `auth` is "api-key"
  • — the node's `keyStore` is false
  • — the node has at least one incoming edge from an app-server, worker or client
  • — this does not hold:
  • — the design contains a node of kind key-management
stateful-node-without-zone-redundancy

A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.

  • — all of these hold:
  • — the node's `stateless` is false
  • — the node sits inside exactly 1 availability-zone group
  • — this does not hold:
  • — the node sits inside at least one cell group
Use it in a design
nodes:
  - { id: "personalize", component: "aws-personalize" }
Other AI service products · 125
Content Moderationalibaba-content-moderationalibabacloudai-serviceFraud Detectionalibaba-fraud-detectionalibabacloudai-serviceID Verificationalibaba-id-verificationalibabacloudai-serviceIntelligent Robotalibaba-intelligent-robotalibabacloudai-serviceModel Studioalibaba-model-studioalibabacloudai-serviceSmart Conversation Analysisalibaba-smart-conversation-analysisalibabacloudai-serviceAmazon Bedrockaws-bedrockawsai-serviceAmazon Bedrock AgentCoreaws-bedrock-agentcoreawsai-serviceAmazon Bedrock Data Automationaws-bedrock-data-automationawsai-serviceAmazon Bedrock Guardrailsaws-bedrock-guardrailsawsai-serviceAmazon Comprehendaws-comprehendawsai-serviceAmazon Comprehend Medicalaws-comprehend-medicalawsai-serviceAWS Elemental Inferenceaws-elemental-inferenceawsai-serviceAmazon Forecastaws-forecastawsai-serviceAmazon Fraud Detectoraws-fraud-detectorawsai-serviceAWS HealthScribeaws-healthscribeawsai-serviceAmazon Lex botaws-lexawsai-serviceAmazon Lookout for Equipmentaws-lookout-for-equipmentawsai-serviceAmazon Lookout for Metricsaws-lookout-for-metricsawsai-serviceAmazon Lookout for Visionaws-lookout-for-visionawsai-serviceAmazon Pollyaws-pollyawsai-serviceAmazon Q Businessaws-q-businessawsai-serviceAmazon Rekognitionaws-rekognitionawsai-serviceAmazon Textractaws-textractawsai-serviceAmazon Transcribeaws-transcribeawsai-serviceAmazon Translateaws-translateawsai-serviceContent Safetyazure-ai-content-safetyazureai-serviceAzure AI Custom Visionazure-ai-custom-visionazureai-serviceAzure AI Faceazure-ai-faceazureai-serviceAzure Languageazure-ai-languageazureai-serviceAzure Speechazure-ai-speechazureai-serviceAzure Translatorazure-ai-translatorazureai-serviceAzure Visionazure-ai-visionazureai-serviceAzure Content Understandingazure-content-understandingazureai-serviceMicrosoft Discoveryazure-discoveryazureai-serviceAzure Document Intelligenceazure-document-intelligenceazureai-serviceFoundry Agent Serviceazure-foundry-agent-serviceazureai-serviceFoundry Modelsazure-foundry-modelsazureai-serviceAzure AI Immersive Readerazure-immersive-readerazureai-serviceAzure OpenAI in Foundry Modelsazure-openaiazureai-service
and 85 more → AI service page
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Amazon Personalize: managed recommendation service that trains on interaction, user and item datasets and serves recommendations from a campaign, a domain recommender or a batch inference job.
# "Amazon Personalize endpoints and quotas" gives the defaults: 5 active dataset groups per Region, 10 solutions, 5 campaigns and 5 recommenders per dataset group, 500 GetRecommendations requests per second per campaign, 1,000 PutEvents per second per dataset group and a 1,000-interaction minimum before training.
schemaVersion: "1"
type: "component"
id: "aws-personalize"
kind: "ai-service"
provider: "aws"
docs: "https://docs.aws.amazon.com/personalize/latest/dg/limits.html"
defaults:
  auth: "iam"
  modality: "structured"
  managed: true
  publicEndpoint: true
  customerManagedKeys: false
properties:
  servingMode:
    type: "enum"
    values: ["campaign", "recommender", "batch-inference"]
    default: "campaign"
  requestsPerSecondPerCampaign:
    type: "integer"
    default: 500
  campaignsPerDatasetGroup:
    type: "integer"
    default: 5
  putEventsPerSecond:
    type: "integer"
    default: 1000
  realTimeEventIngestion:
    type: "boolean"
    default: false

The same page as markdown, for an agent: /catalogue/components/aws-personalize.md