diff options
| author | Roger Gonzalez <roger@rogs.me> | 2020-04-27 13:29:49 -0300 |
|---|---|---|
| committer | Roger Gonzalez <roger@rogs.me> | 2020-04-27 13:29:49 -0300 |
| commit | fa4fdfecc5963b1db291b5734ca1b309351b3e83 (patch) | |
| tree | 3d75e4c0f35cd3b0cfd559f31766fa74454c9669 | |
| parent | 870acd5c0157b7e8a7698d90974c5417c5cd9b3e (diff) | |
Published the new ddos post
| -rw-r--r-- | content/posts/secure-api-with-nginx-and-fail2ban.md | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/content/posts/secure-api-with-nginx-and-fail2ban.md b/content/posts/secure-api-with-nginx-and-fail2ban.md index 83bc0a9..e2e579c 100644 --- a/content/posts/secure-api-with-nginx-and-fail2ban.md +++ b/content/posts/secure-api-with-nginx-and-fail2ban.md @@ -3,7 +3,6 @@ title: "Secure your Django API from DDoS attacks with NGINX and fail2ban" date: 2020-04-26T11:36:39-03:00 lastmod: 2020-04-26T11:36:39-03:00 tags : [ "devops", "nginx", "django" ] -draft : true --- Hello everyone! @@ -162,6 +161,13 @@ And it will return something like: And that's it! It is fully working, you are now protected from DDoS attacks dynamically. +# Django configuration + +For Django things are easy. There is no configuration needed, but if you use the Admin +or REST viewer in any form, you might want to run a separate instance just for that. +In our experience, we got blocked a bunch of times so now we are running the admin and +some cron jobs on a second medium EC2 instance. + # Bonus ## What if I want to ban an IP address forever? |