Skip to content

Publish default for concurrency #2708

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 27, 2025
Merged

Publish default for concurrency #2708

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/2.0/docs/accountfactory/guides/drift-remediation-with-async-module.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ To avoid hitting that limit (and prevent failed updates), you can configure the

```hcl
inputs = {
lambda_worker_max_concurrent_operations = X
lambda_worker_max_concurrent_operations = X # default is 4
}
```

Expand All @@ -135,5 +135,6 @@ This variable tells the worker Lambda to never initiate more than X updates at a
|Value | Behavior |
| -- | -- |
|`5` | Max concurrency allowed by AWS (use with caution) |
|`4` | The default set by the async module |
|`<5` | Safe concurrency with headroom for other ops |
|`1` | Serialized updates, safest but slowest |