Amazon Lookout for Equipment

awsAI serviceaws-lookout-for-equipment

Managed anomaly detection that spots abnormal behaviour in industrial sensor data.

Provider
aws
Category
Compute
Properties · 5 set by this component
propertytypevaluesrequiredkind defaultthis component
authenumapi-key | oauth | iam | noneno—▸ iam
contentFilteringboolean—no—inherited
customerManagedKeysboolean—no—▸ false
dataResidency · advancedenumus | eu | asia | globalno—inherited
dataRetentionDaysinteger—no—inherited
inferenceFrequencyMinutes · component propertyinteger—no—inherited
keyStoreboolean—nofalseinherited
labelledFailureData · component propertyboolean—nofalseinherited
managedboolean—nofalse▸ true
maxSensorsPerModel · component propertyinteger—no300inherited
modalityenumtext | vision | speech | multimodal | structured | image | video | audio | embedding | rerankno—▸ structured
offConditionSensor · component propertyboolean—nofalseinherited
publicEndpointboolean—no—▸ true
quotaUnitsPerMinuteinteger—no—inherited
rateLimitRpm · advancedinteger—no—inherited
rateLimitTpm · advancedinteger—no—inherited
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: "lookout-for-equipment", component: "aws-lookout-for-equipment" }
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 Metricsaws-lookout-for-metricsawsai-serviceAmazon Lookout for Visionaws-lookout-for-visionawsai-serviceAmazon Personalizeaws-personalizeawsai-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 Lookout for Equipment: managed anomaly detection for industrial equipment that trains on historical sensor data in Amazon S3 and runs an inference scheduler over new readings. Sunset, end of support 7 October 2026; placeable until end of support.
# "What is Amazon Lookout for Equipment?" states a single model covers up to 300 sensors, that training data is uploaded to an Amazon S3 bucket and that the trained model is deployed to process new sensor data; "CreateInferenceScheduler" gives the data upload frequency choices of 5, 10, 15, 30 and 60 minutes, which is also how often inference runs, and leaves the choice required rather than defaulted.
schemaVersion: "1"
type: "component"
id: "aws-lookout-for-equipment"
kind: "ai-service"
provider: "aws"
docs: "https://docs.aws.amazon.com/lookout-for-equipment/latest/ug/what-is.html"
defaults:
  auth: "iam"
  modality: "structured"
  managed: true
  publicEndpoint: true
  customerManagedKeys: false
properties:
  inferenceFrequencyMinutes:
    type: "integer"
  maxSensorsPerModel:
    type: "integer"
    default: 300
  labelledFailureData:
    type: "boolean"
    default: false
  offConditionSensor:
    type: "boolean"
    default: false

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