Skip to content

Commit

Permalink
chore: Update crowdsec-bunkerweb-bouncer version to v1.6
Browse files Browse the repository at this point in the history
  • Loading branch information
TheophileDiot committed Jun 24, 2024
1 parent 1fa4405 commit 811b472
Showing 1 changed file with 13 additions and 3 deletions.
16 changes: 13 additions & 3 deletions crowdsec/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ labels:
For container-based integrations, we recommend you to redirect the logs of the BunkerWeb container to a syslog service that will store the logs so CrowdSec can access it easily. Here is an example configuration for syslog-ng that will store raw logs coming from BunkerWeb to a local `/var/log/bunkerweb.log` file :

```conf
@version: 4.6
@version: 4.7
source s_net {
udp(
Expand Down Expand Up @@ -74,6 +74,7 @@ services:
- "bunkerweb.INSTANCE=yes"
environment:
- SERVER_NAME=www.example.com
- API_WHITELIST_IP=127.0.0.0/24 10.20.30.0/24
- USE_CROWDSEC=yes
- CROWDSEC_API=http://crowdsec:8080
- CROWDSEC_APPSEC_URL=http://crowdsec:7422
Expand All @@ -84,6 +85,7 @@ services:
networks:
- bw-universe
- bw-services
- bw-plugins
logging:
driver: syslog
options:
Expand Down Expand Up @@ -120,15 +122,15 @@ services:
- BOUNCER_KEY_bunkerweb=s3cr3tb0unc3rk3y
- COLLECTIONS=crowdsecurity/nginx
networks:
- bw-universe
- bw-plugins
syslog:
image: balabit/syslog-ng:4.7.1
volumes:
- ./syslog-ng.conf:/etc/syslog-ng/syslog-ng.conf
- bw-logs:/var/log
networks:
bw-universe:
bw-plugins:
ipv4_address: 10.10.10.254
myapp:
Expand All @@ -140,6 +142,11 @@ networks:
bw-docker:
bw-services:
bw-universe:
ipam:
driver: default
config:
- subnet: 10.20.30.0/24
bw-plugins:
ipam:
driver: default
config:
Expand All @@ -151,6 +158,9 @@ volumes:
cs-data:
```

> [!TIP]
> The `balabit/syslog-ng` image used in the example is only compatible with amd64 architecture. If you want to use an arm64 compatible image, you can use `lscr.io/linuxserver/syslog-ng` instead.

## Kubernetes

The recommended way of installing CrowdSec in your Kubernetes cluster is by using their official [helm chart](https://github.com/crowdsecurity/helm-charts). You will find a tutorial [here](https://crowdsec.net/blog/kubernetes-crowdsec-integration/) for more information. By doing so, a syslog service is no more mandatory because agents will forward BunkerWeb logs to the CS API.
Expand Down

0 comments on commit 811b472

Please sign in to comment.