From 227cbb582b9899de2e4e7cc0a3555871d9190c1c Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Tue, 12 Nov 2024 16:36:47 +0100 Subject: [PATCH 1/4] docs(srv): add ref on DNS query rate limit for faas caas MTA-5249 --- macros/serverless/dns-query-rate-limit.mdx | 54 +++++++++++++++++++ menu/navigation.json | 8 +++ .../reference-content/dns-rate-limit.mdx | 17 ++++++ .../reference-content/dns-rate-limit.mdx | 17 ++++++ 4 files changed, 96 insertions(+) create mode 100644 macros/serverless/dns-query-rate-limit.mdx create mode 100644 serverless/containers/reference-content/dns-rate-limit.mdx create mode 100644 serverless/functions/reference-content/dns-rate-limit.mdx diff --git a/macros/serverless/dns-query-rate-limit.mdx b/macros/serverless/dns-query-rate-limit.mdx new file mode 100644 index 0000000000..fb9e93f294 --- /dev/null +++ b/macros/serverless/dns-query-rate-limit.mdx @@ -0,0 +1,54 @@ +--- +macro: dns-query-rate-limit +--- + +## DNS Query Rate Limiting + +To ensure the stability and performance of our Serverless Functions and Containers platform, we have implemented a rate limit to the number of DNS queries that can be made by users. This rate limit is designed to prevent any single container instance from consuming excessive resources and impacting the performance of other users' functions and containers. + +## Rate Limit Details + +The rate limit is set at **20 requests per second per function or container instance**. + +This limit only applies to DNS queries that require a full resolution, such as queries for records that have not been previously resolved. +Queries for records that have already been resolved recently are not subject to this rate limit. + + +The rate limit is applied per function or container instance, not per user or client. + +The rate limit is therefore enforced independently for each function or container instance, regardless of the user or client that owns it. + + +## Effective Date + +The DNS query rate limit will be enforced starting on November, 26th 2024. Any DNS queries made after this time will be subject to the rate limit. + +## Why Rate Limiting is Necessary + +Our Serverless Functions and Containers platform is a shared infrastructure, which means that multiple users' functions or containers are running on the same nodes. In the past, we have experienced issues with high DNS query volumes from some function or container instances, which have impacted the performance of other users' containers. These issues have led to DNS resolution delays, timeouts, and other problems that affect the overall stability and performance of our platform. + +To mitigate these issues, we have implemented rate limiting on DNS queries. By limiting the number of DNS queries that can be made by each function or container instance, we can prevent any single instance from consuming all available DNS resources and causing problems for other users. + + +The 20 requests per second limit is far above the typical usage patterns we have seen from legitimate users, and it only applies to DNS queries that require a full resolution. Therefore, this rate limit should not impact most users. + + +## Impact on Legitimate Users + +We understand that rate limiting may restrict some users' activities, but we believe that this is a necessary measure to ensure the overall stability and performance of our platform. Legitimate users who are making reasonable use of our platform should not be affected by this rate limit. In fact, rate limiting will help to ensure that our platform remains responsive and high-performing for all users, even in case of high traffic or malicious activity. + +## Optimizing DNS Query Usage + +If you are experiencing issues with the DNS query rate limit, review your application's DNS query usage to see if there are any opportunities for optimization. + +However, this rate limit is intended to prevent excessive DNS query volumes, and most users should not need to take any action to avoid hitting the limit. + +## Future Changes to the Rate Limit + +Scaleway reserves the right to adjust the rate limit in the future as needed to ensure the stability and performance of our platform. We will notify users of any changes to the rate limit through our usual communication channels. + +## Additional Support + +If you have specific needs that require a higher DNS query volume, you may be able to implement optimizations on the application side to reduce the number of DNS queries made. + +[Contact the Scaleway Support](https://console.scaleway.com/support/tickets/create) for assistance if you encounter any issues or have questions about the DNS query rate limit. We're here to help you get the most out of our platform. diff --git a/menu/navigation.json b/menu/navigation.json index 5eb5a53088..5a9d50b0dd 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -3762,6 +3762,10 @@ { "label": "Cron schedules reference", "slug": "cron-schedules" + }, + { + "label": "DNS query rate limiting", + "slug": "dns-query-rate-limit" } ], "label": "Additional Content", @@ -3904,6 +3908,10 @@ { "label": "Cron schedules reference", "slug": "cron-schedules" + }, + { + "label": "DNS query rate limiting", + "slug": "dns-query-rate-limit" } ], "label": "Additional Content", diff --git a/serverless/containers/reference-content/dns-rate-limit.mdx b/serverless/containers/reference-content/dns-rate-limit.mdx new file mode 100644 index 0000000000..f4759db9c0 --- /dev/null +++ b/serverless/containers/reference-content/dns-rate-limit.mdx @@ -0,0 +1,17 @@ +--- +meta: + title: DNS query rate limiting + description: Information on how the DNS query rate limiting works with Scaleway Serverless Containers. +content: + h1: DNS query rate limiting + paragraph: Information on how the DNS query rate limiting works with Scaleway Serverless Containers. +tags: serverless containers dns query rate limiting limit response ddos +dates: + validation: 2024-11-12 + posted: 2024-11-12 +categories: + - serverless + - containers +--- + + \ No newline at end of file diff --git a/serverless/functions/reference-content/dns-rate-limit.mdx b/serverless/functions/reference-content/dns-rate-limit.mdx new file mode 100644 index 0000000000..2f268d6f7c --- /dev/null +++ b/serverless/functions/reference-content/dns-rate-limit.mdx @@ -0,0 +1,17 @@ +--- +meta: + title: DNS query rate limiting + description: Information on how the DNS query rate limiting works with Scaleway Serverless Functions. +content: + h1: DNS query rate limiting + paragraph: Information on how the DNS query rate limiting works with Scaleway Serverless Functions. +tags: serverless functions dns query rate limiting limit response ddos +dates: + validation: 2024-11-12 + posted: 2024-11-12 +categories: + - serverless + - functions +--- + + From 73aeb5fdf00011aefe86fb3e2ae549d90ca018a3 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Tue, 12 Nov 2024 16:39:38 +0100 Subject: [PATCH 2/4] docs(srv): update file names --- .../{dns-rate-limit.mdx => dns-query-rate-limit.mdx} | 0 .../{dns-rate-limit.mdx => dns-query-rate-limit.mdx} | 0 2 files changed, 0 insertions(+), 0 deletions(-) rename serverless/containers/reference-content/{dns-rate-limit.mdx => dns-query-rate-limit.mdx} (100%) rename serverless/functions/reference-content/{dns-rate-limit.mdx => dns-query-rate-limit.mdx} (100%) diff --git a/serverless/containers/reference-content/dns-rate-limit.mdx b/serverless/containers/reference-content/dns-query-rate-limit.mdx similarity index 100% rename from serverless/containers/reference-content/dns-rate-limit.mdx rename to serverless/containers/reference-content/dns-query-rate-limit.mdx diff --git a/serverless/functions/reference-content/dns-rate-limit.mdx b/serverless/functions/reference-content/dns-query-rate-limit.mdx similarity index 100% rename from serverless/functions/reference-content/dns-rate-limit.mdx rename to serverless/functions/reference-content/dns-query-rate-limit.mdx From b9cd105c82846a78f472ec622978be72cc683856 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Tue, 12 Nov 2024 16:43:42 +0100 Subject: [PATCH 3/4] docs(srv): tech review --- .../containers/reference-content/dns-query-rate-limit.mdx | 2 +- serverless/functions/reference-content/dns-query-rate-limit.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/serverless/containers/reference-content/dns-query-rate-limit.mdx b/serverless/containers/reference-content/dns-query-rate-limit.mdx index f4759db9c0..1494f93fd3 100644 --- a/serverless/containers/reference-content/dns-query-rate-limit.mdx +++ b/serverless/containers/reference-content/dns-query-rate-limit.mdx @@ -5,7 +5,7 @@ meta: content: h1: DNS query rate limiting paragraph: Information on how the DNS query rate limiting works with Scaleway Serverless Containers. -tags: serverless containers dns query rate limiting limit response ddos +tags: serverless containers dns query rate limiting limit response dates: validation: 2024-11-12 posted: 2024-11-12 diff --git a/serverless/functions/reference-content/dns-query-rate-limit.mdx b/serverless/functions/reference-content/dns-query-rate-limit.mdx index 2f268d6f7c..9aee0ccffa 100644 --- a/serverless/functions/reference-content/dns-query-rate-limit.mdx +++ b/serverless/functions/reference-content/dns-query-rate-limit.mdx @@ -5,7 +5,7 @@ meta: content: h1: DNS query rate limiting paragraph: Information on how the DNS query rate limiting works with Scaleway Serverless Functions. -tags: serverless functions dns query rate limiting limit response ddos +tags: serverless functions dns query rate limiting limit response dates: validation: 2024-11-12 posted: 2024-11-12 From d8e5c03bc6b773c961c83ee0f2adb8d77e9cc61e Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Thu, 14 Nov 2024 10:40:13 +0100 Subject: [PATCH 4/4] docs(srv): tech review --- macros/serverless/dns-query-rate-limit.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/macros/serverless/dns-query-rate-limit.mdx b/macros/serverless/dns-query-rate-limit.mdx index fb9e93f294..5403cc9fdc 100644 --- a/macros/serverless/dns-query-rate-limit.mdx +++ b/macros/serverless/dns-query-rate-limit.mdx @@ -2,11 +2,11 @@ macro: dns-query-rate-limit --- -## DNS Query Rate Limiting +## DNS query Rate limiting To ensure the stability and performance of our Serverless Functions and Containers platform, we have implemented a rate limit to the number of DNS queries that can be made by users. This rate limit is designed to prevent any single container instance from consuming excessive resources and impacting the performance of other users' functions and containers. -## Rate Limit Details +## Rate limit details The rate limit is set at **20 requests per second per function or container instance**. @@ -19,11 +19,11 @@ The rate limit is applied per function or container instance, not per user or cl The rate limit is therefore enforced independently for each function or container instance, regardless of the user or client that owns it. -## Effective Date +## Effective date The DNS query rate limit will be enforced starting on November, 26th 2024. Any DNS queries made after this time will be subject to the rate limit. -## Why Rate Limiting is Necessary +## Why rate limiting is necessary Our Serverless Functions and Containers platform is a shared infrastructure, which means that multiple users' functions or containers are running on the same nodes. In the past, we have experienced issues with high DNS query volumes from some function or container instances, which have impacted the performance of other users' containers. These issues have led to DNS resolution delays, timeouts, and other problems that affect the overall stability and performance of our platform. @@ -33,21 +33,21 @@ To mitigate these issues, we have implemented rate limiting on DNS queries. By l The 20 requests per second limit is far above the typical usage patterns we have seen from legitimate users, and it only applies to DNS queries that require a full resolution. Therefore, this rate limit should not impact most users. -## Impact on Legitimate Users +## Impact on legitimate users We understand that rate limiting may restrict some users' activities, but we believe that this is a necessary measure to ensure the overall stability and performance of our platform. Legitimate users who are making reasonable use of our platform should not be affected by this rate limit. In fact, rate limiting will help to ensure that our platform remains responsive and high-performing for all users, even in case of high traffic or malicious activity. -## Optimizing DNS Query Usage +## Optimizing DNS query usage If you are experiencing issues with the DNS query rate limit, review your application's DNS query usage to see if there are any opportunities for optimization. However, this rate limit is intended to prevent excessive DNS query volumes, and most users should not need to take any action to avoid hitting the limit. -## Future Changes to the Rate Limit +## Future changes to the rate limit Scaleway reserves the right to adjust the rate limit in the future as needed to ensure the stability and performance of our platform. We will notify users of any changes to the rate limit through our usual communication channels. -## Additional Support +## Additional support If you have specific needs that require a higher DNS query volume, you may be able to implement optimizations on the application side to reduce the number of DNS queries made.