andwati/zitadel
1
0
Fork 0
mirror of https://github.com/andwati/zitadel.git synced 2026-11-02 20:32:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Update production guidelines (#12552)

Browse Source
This commit is contained in:
Maximilian
2026-08-07 10:48:21 +02:00
committed by GitHub
parent be5b278069
commit 9fa0cad9d9
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/content/self-hosting/manage/production.mdx
+1 -2
View File
@@ -201,8 +201,7 @@ DefaultInstance:
## Limits and Quotas
If you host ZITADEL as a service,
you might want to [limit usage and/or execute tasks on certain usage units and levels](/self-hosting/manage/usage_control).
We strongly advise implementing [rate limiting](/self-hosting/manage/usage_control) and bot detection. Even with robust cryptography, reducing request volume helps protect against brute-force and denial-of-service attacks.
## Minimum system requirements
apps/docs/content/self-hosting/manage/productionchecklist.mdx
+2 -1
View File
@@ -34,7 +34,8 @@ To apply best practices to your production setup we created a step by step check
- [ ] Use a Layer 7 Web Application Firewall to secure ZITADEL that supports **[HTTP/2](/self-hosting/manage/http2)**
- [ ] Limit the access by IP addresses if needed
- [ ] Secure the access by rate limits for specific endpoints (e.g. API vs frontend) to secure availability on high load. See the [ZITADEL Cloud rate limits](/legal/policies/rate-limit-policy) for reference.
- [ ] Implement rate limiting for specific endpoints (e.g. API vs frontend) to protect against brute-force and denial-of-service attacks. See the [ZITADEL Cloud rate limits](/legal/policies/rate-limit-policy) for reference.
- [ ] Implement bot detection to reduce automated abuse
- [ ] Check that your firewall also filters IPv6 traffic
### ZITADEL setup