AWS Systems Manager

awsWorkeraws-systems-manager

Operates managed nodes across AWS, on-premises and multicloud with Automation, Run Command, State Manager and Patch Manager.

Provider
aws
Kind
Worker
Category
Compute
Also known as
SSM
Properties · 2 set by this component
propertytypevaluesrequiredkind defaultthis component
acceleratorenumnone | gpu | asicnononeinherited
agentRequired · component propertyboolean—notrueinherited
concurrencyinteger—no—inherited
fanoutStrategy · advancedenumnone | push | pull | hybridnononeinherited
fanoutThreshold · advancedinteger—no—inherited
hybridNodes · component propertyboolean—notrueinherited
idempotentboolean—nofalseinherited
instancesinteger—no—inherited
managedboolean—nofalse▸ true
rateControl · advancedenumnone | fixed | aimdnononeinherited
schedulestring—no—inherited
tool · component propertyenumautomation | run-command | state-manager | patch-manager | maintenance-window | inventoryno—inherited
triggerenumqueue | stream | schedule | batch | manualyes—▸ manual
Rules that apply · 3

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.

push-fanout-without-celebrity-path

Pure push fan-out over a social graph is brutal at the tail: one post from an account with millions of followers becomes millions of cache writes. A follower threshold above which readers merge at read time bounds that write amplification.

  • — all of these hold:
  • — the node's `fanoutStrategy` is "push"
  • — the node's `fanoutThreshold` has no value
  • — the design contains a node of kind graph-database
shared-worker-pool-across-queues

One worker pool consuming several queues lets a slow or poisoned queue starve the others. That is precisely what the design's per-queue isolation requirement forbids.

  • — all of these hold:
  • — the node has more than 1 incoming edge from a queue
  • — the design requirement `isolation.perQueue` is true
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: "systems-manager", component: "aws-systems-manager" }
Other Worker products · 82
SchedulerXalibaba-schedulerxalibabacloudworkerAmazon AppFlowaws-appflowawsworkerAWS B2B Data Interchangeaws-b2b-data-interchangeawsworkerAWS Batchaws-batchawsworkerAWS Glue DataBrewaws-databrewawsworkerAWS DataSyncaws-datasyncawsworkerAWS Deadline Cloudaws-deadline-cloudawsworkerAWS Entity Resolutionaws-entity-resolutionawsworkerAmazon EventBridge Scheduleraws-eventbridge-schedulerawsworkerAWS Fault Injection Serviceaws-fisawsworkerAWS Glue crawleraws-glue-crawlerawsworkerAWS Glue for Ray jobaws-glue-ray-jobawsworkerAWS Application Migration Serviceaws-mgnawsworkerAmazon MSK Connectaws-msk-connectawsworkerAmazon SageMaker AI Training Jobaws-sagemaker-training-jobawsworkerAWS Thinkbox Deadline 10aws-thinkbox-deadlineawsworkerAWS Glue jobglue-jobawsworkerAzure Automationazure-automationazureworkerAzure Batchazure-batchazureworkerAzure Chaos Studioazure-chaos-studioazureworkerAzure Data Factoryazure-data-factoryazureworkerAzure Data Shareazure-data-shareazureworkerAzure Database Migration Serviceazure-database-migration-serviceazureworkerMicrosoft Entra Connect Syncazure-entra-connect-syncazureworkerMicrosoft Graph Data Connectazure-graph-data-connectazureworkerAzure Storage Moverazure-storage-moverazureworkerAzure Update Managerazure-update-managerazureworkerBrowser Runcloudflare-browser-runcloudflareworkerCloudflare Snippetscloudflare-snippetscloudflareworkerCloudflare Zarazcloudflare-zarazcloudflareworkerAirbyteairbyteworkerAirflow DAGairflow-dagworkerChaos Meshchaos-meshworkerChunkrchunkrworkerContainer workercontainer-workerworkerCron jobcron-jobworkerDaytonadaytonaworkerE2Be2bworkerEmbulkembulkworkerFan-out daemonfanout-daemonworker
and 42 more → Worker page
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# AWS Systems Manager: operates managed nodes across AWS, on-premises and multicloud environments through
# Automation, Run Command, State Manager and Patch Manager. Per "What is AWS Systems Manager?" a node is
# managed only once SSM Agent is installed and reachable, and tasks are run on demand unless scheduled.
schemaVersion: "1"
type: "component"
id: "aws-systems-manager"
kind: "worker"
provider: "aws"
docs: "https://docs.aws.amazon.com/systems-manager/latest/userguide/what-is-systems-manager.html"
aliases: ["SSM"]
defaults:
  trigger: "manual"
  managed: true
properties:
  tool:
    type: "enum"
    values: ["automation", "run-command", "state-manager", "patch-manager", "maintenance-window", "inventory"]
  agentRequired:
    type: "boolean"
    default: true
  hybridNodes:
    type: "boolean"
    default: true

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