Skip to content
Proud to collaborate with Microsoft for Startups

runner.execution-launch-ec2 ​

Launch one runner execution on EC2 Auto Scaling

Launch a new ECS task for an EC2 Auto Scaling-backed runner group.

Identical to RunnerExecutionLaunchWorkflow except:

  • run_task uses the group ECS capacity provider strategy
  • No networkConfiguration block (EC2 bridge mode does not use awsvpc)
  • Backend guard uses ensure_ec2_runner_group

Overview ​

PropertyValue
Workflow typeLinear
LibraryApp-runners-aws
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
runner_group_uuiduuidYes—Runner group UUID
organization_uuiduuidYes—Organization UUID
runner_execution_uuiduuidNo—Existing execution UUID to reuse
environmentdictNo—Environment variables to pass to container. Sensitive (SECRET-HANDLING-001): values are vaulted rather than persisted in workflow state_data, and only the key names are recorded on the execution record
commandlistNo—Optional command override for container
runner_imagestringNo—Optional custom container image for this execution

Output Schema ​

FieldTypeRequiredDefaultDescription
runner_group_uuiduuidNo—UUID of the RunnerGroup this workflow operates on, picked from the organization's list of runner groups. Optional on this shared passthrough schema because the same field also appears as an output-only echo.
organization_uuiduuidNo—UUID of the caller's organization, injected server-side from the authenticated request; scopes the operation to the correct tenant.
registry_account_uuiduuidNo—UUID of the container registry account this runner group resolves images against, picked from the organization's registry accounts. Optional — falls back to default/unauthenticated image resolution when absent.
actor_uuiduuidNo—UUID of the user or service actor who triggered this action, injected server-side from the authenticated request when available; used for audit/attribution only.
workflow_run_idstringNo——
workflow_run_uuidstringNo—Legacy alias of workflow_run_id: an internal engine correlation/run identifier for this DAG execution (ADR-015/E1 plumbing), not a foreign key to any business entity. No list/query workflow applies — this is engine-generated, never user-supplied.
workflow_uuidstringNo—Engine workflow-run identifier associated with this record; not a platform entity foreign key despite the name. No list/query workflow applies — this is engine-generated, never user-supplied.
statusstringNo——
outcomestringNo——
initiated_atstringNo——
completed_atstringNo——
failed_atstringNo——
failure_reasonstringNo——
errorstringNo——
error_typestringNo——
reasonstringNo——
failed_stepjsonNo——
failed_layerjsonNo——
failed_at_statejsonNo——
compensation_triggerjsonNo——
comp_current_layerjsonNo——
comp_queuejsonNo——
comp_retry_countjsonNo——
primitive_inputjsonNo——
primitive_outputjsonNo——
environmentjsonNo—Credential-bearing field (SECRET-HANDLING-001): vaulted by SensitiveDataMiddleware instead of being persisted in cleartext state_data / event history.
commandjsonNo——
runner_imagejsonNo——
registration_tokenjsonNo—Credential-bearing field (SECRET-HANDLING-001): vaulted by SensitiveDataMiddleware instead of being persisted in cleartext state_data / event history.
task_arnjsonNo——
container_namejsonNo——
step_outputjsonNo——
runner_execution_uuidjsonNo——
cluster_arnjsonNo——
log_group_namejsonNo——
needs_custom_imagejsonNo——
task_definition_arnjsonNo——
runner_namejsonNo——
runtime_envjsonNo—Credential-bearing field (SECRET-HANDLING-001): vaulted by SensitiveDataMiddleware instead of being persisted in cleartext state_data / event history.
start_commandjsonNo——
last_statusjsonNo——
environment_keysjsonNo——

States ​

StateInitialTerminalSuccessAuto-advanceDescription
initiatedYesNo—prepare—
building_start_commandNoNo—launch_task—
getting_registration_tokenNoNo—build_start_command—
launching_taskNoNo—complete—
preparingNoNo—get_registration_token—
completedNoYesYes——
failedNoYesNo——

State Diagram ​

Transitions ​

FromActionToDescription
initiatedpreparepreparing—
preparingget_registration_tokengetting_registration_token—
getting_registration_tokenbuild_start_commandbuilding_start_command—
building_start_commandlaunch_tasklaunching_task—
launching_taskcompletecompleted—
* (any state)failfailed—

API Usage ​

bash
POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "runner.execution-launch-ec2",
  "initial_data": {
    "runner_group_uuid": "value",
    "organization_uuid": "value"
  }
}