Skip to content

Commit acae897

Browse files
Update modules/runners/README.md
Co-authored-by: Gertjan Maas <[email protected]>
1 parent ce1afb8 commit acae897

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

modules/runners/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ The action runners are created via a launch template; in the launch template onl
1010

1111
### Lambda scale up
1212

13-
The scale up lambda is triggered by events on an SQS queue. Events on this queue are delayed, which will give the workflow some time to start running on available runners. For each event the lambda will check if the workflow is still queued and no other limits are reached. In that case the lambda will create a new EC2 instance. The lambda only needs to know which launch template to use and which subnets are available. From the available subnets a random one will be chosen. Once the instance is created the event is assumed as handled, and we assume the workflow wil start at some moment once the created instance is ready.
13+
The scale up lambda is triggered by events on a SQS queue. Events on this queue are delayed, which will give the workflow some time to start running on available runners. For each event the lambda will check if the workflow is still queued and no other limits are reached. In that case the lambda will create a new EC2 instance. The lambda only needs to know which launch template to use and which subnets are available. From the available subnets a random one will be chosen. Once the instance is created the event is assumed as handled, and we assume the workflow wil start at some moment once the created instance is ready.
1414

1515
### Lambda scale down
1616

0 commit comments

Comments
 (0)