Skip to content

Commit a7db8dd

Browse files
authored
mention stop timeout for aws-waf-bouncer in docker (#659)
1 parent f20bbaa commit a7db8dd

1 file changed

Lines changed: 12 additions & 1 deletion

File tree

crowdsec-docs/unversioned/bouncers/aws-waf.mdx

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,9 +71,20 @@ sudo yum install crowdsec-aws-waf-bouncer
7171
### Docker
7272

7373
```shell
74-
docker run -v $(PWD)/config.yaml:/cs-aws-waf-bouncer.yaml crowdsecurity/aws-waf-bouncer
74+
docker run -e BOUNCER_CONFIG_FILE=/cs-aws-waf-bouncer.yaml -v $(PWD)/config.yaml:/cs-aws-waf-bouncer.yaml crowdsecurity/aws-waf-bouncer
7575
```
7676

77+
:::info
78+
79+
The remediation component can take some time to delete all created resources on shutdown.
80+
81+
The default docker timeout of 10s before sending a `SIGKILL` to the process might not always been enough.
82+
83+
You can increase it by specifying `--stop-timeout` in your `run` command or by setting `stop_grace_period` when using compose.
84+
85+
:::
86+
87+
7788
## Configuration Reference
7889

7990
You will need to edit `/etc/crowdsec/bouncers/crowdsec-aws-waf-bouncer.yaml` to configure the ACLs you want the component to use.

0 commit comments

Comments
 (0)