Storage Transfer Service

gcpWorkergoogle-storage-transfer-service

Managed transfer job copying objects and files into Cloud Storage.

Provider
gcp
Kind
Worker
Category
Compute
Also known as
STS
Properties · 3 set by this component
propertytypevaluesrequiredkind defaultthis component
acceleratorenumnone | gpu | asicnononeinherited
concurrencyinteger—no—inherited
deleteSourceAfterTransfer · component propertyboolean—nofalseinherited
fanoutStrategy · advancedenumnone | push | pull | hybridnononeinherited
fanoutThreshold · advancedinteger—no—inherited
idempotentboolean—nofalse▸ true
instancesinteger—no—inherited
managedboolean—nofalse▸ true
overwriteBehavior · component propertyenumif-different | always | nevernoif-differentinherited
rateControl · advancedenumnone | fixed | aimdnononeinherited
schedulestring—no—inherited
scheduleMode · component propertyenumrun-once | recurringnorun-onceinherited
transferMode · component propertyenumagentless | agent-basednoagentlessinherited
triggerenumqueue | stream | schedule | batch | manualyes—▸ batch
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: "storage-transfer-service", component: "google-storage-transfer-service" }
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 Systems Manageraws-systems-managerawsworkerAWS 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-jobworkerDaytonadaytonaworkerE2Be2bworkerEmbulkembulkworker
and 42 more → Worker page
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Storage Transfer Service transfer job: managed copy of objects or files into Cloud Storage.
# "Create transfers" states a job runs once by default, deletion of source and of extra
# destination objects both default to Never, and objects are overwritten only "if different";
# "Storage Transfer Service overview" states all HTTPS traffic uses TLS 1.3.
schemaVersion: "1"
type: "component"
id: "google-storage-transfer-service"
kind: "worker"
provider: "gcp"
docs: "https://cloud.google.com/storage-transfer/docs/create-transfers"
aliases: ["STS"]
defaults:
  trigger: "batch"
  idempotent: true
  managed: true
properties:
  transferMode:
    type: "enum"
    values: ["agentless", "agent-based"]
    default: "agentless"
  scheduleMode:
    type: "enum"
    values: ["run-once", "recurring"]
    default: "run-once"
  overwriteBehavior:
    type: "enum"
    values: ["if-different", "always", "never"]
    default: "if-different"
  deleteSourceAfterTransfer:
    type: "boolean"
    default: false

The same page as markdown, for an agent: /catalogue/components/google-storage-transfer-service.md