.NET 7 Azure Function 中的速率限制

huangapple
go评论77阅读模式
英文:

.NET 7 Rate Limiting in Azure Function

问题

有没有办法在Azure Function v4（dotnet-isolated）的HttpTrigger上使用.NET 7的速率限制？

我已经像这样在我的ConfigureServices中添加了RateLimiter：

  1. var builder = new HostBuilder()
  2.     .ConfigureFunctionsWorkerDefaults()
  3.     .ConfigureServices(s =>
  4.     {
  5.         // ...
  6.         
  7.         s.AddRateLimiter(_ =>
  8.         {
  9.             _.AddPolicy("myfunction", httpContext =>
  10.                 RateLimitPartition.GetSlidingWindowLimiter(httpContext.Request.Headers["X-Forwarded-For"],
  11.                 _ => new SlidingWindowRateLimiterOptions
  12.                 {
  13.                     AutoReplenishment = true,
  14.                     PermitLimit = 1,
  15.                     Window = TimeSpan.FromSeconds(5)
  16.                 }));
  17.         });
  18.     })
  19.     .Build();

和

  1.  [Function("myfunction")]
  2.  [EnableRateLimiting("myfunction")]
  3.  public async Task<IActionResult> MyFunction(
  4.      [HttpTrigger(AuthorizationLevel.Function, "post", Route = null)] HttpRequestData req)
  5.  { // ...
  6.  }

我相当肯定它不应该像这样工作，但这只是为了举例情景。我的架构是Azure静态Web应用-->API管理（注意！消耗计划）-->Azure Function，并且我可以从Azure Function中的“X-Forwarded-For”标头获取有效的客户端IP，但是

因此，是否可能在函数级别对Azure Function应用速率限制策略？

谢谢！

英文:

Is there a way to use .NET 7 Rate Limiting on Azure Function v4 (dotnet-isolated) HttpTrigger?

I've added RateLimiter in my ConfigureServices like this:

  1. var builder = new HostBuilder()
  2.     .ConfigureFunctionsWorkerDefaults()
  3.     .ConfigureServices(s =&gt;
  4.     {
  5.         // ...
  6.         
  7.         s.AddRateLimiter(_ =&gt;
  8.         {
  9.             _.AddPolicy(&quot;myfunction&quot;, httpContext =&gt;
  10.                 RateLimitPartition.GetSlidingWindowLimiter(httpContext.Request.Headers[&quot;X-Forwarded-For&quot;],
  11.                 _ =&gt; new SlidingWindowRateLimiterOptions
  12.                 {
  13.                     AutoReplenishment = true,
  14.                     PermitLimit = 1,
  15.                     Window = TimeSpan.FromSeconds(5)
  16.                 }));
  17.         });
  18.     })
  19.     .Build();

and

  1.  [Function(&quot;myfunction&quot;)]
  2.  [EnableRateLimiting(&quot;myfunction&quot;)]
  3.  public async Task&lt;IActionResult&gt; MyFunction(
  4.      [HttpTrigger(AuthorizationLevel.Function, &quot;post&quot;, Route = null)] HttpRequestData req)
  5.  { // ...
  6.  }

I'm pretty sure it shouldn't even work like this, but just to give an example of the scenario. My architecture is Azure Static Web App --> API Management (NOTE! consumption plan) --> Azure Function, and I can get the valid client IP from the X-Forwarded-For header in the Azure Function, but

So, is it possible to apply the rate limiting policy to a Azure Function on a function level?

Thanks!

答案1

得分: 1

如 @Silent 提到的，您可以在 Azure APIM 消费计划中使用速率限制策略。

您可以将多个函数 API 导入到 Azure APIM 服务，并可以为每个 API 级别添加速率限制策略。
.NET 7 Azure Function 中的速率限制

我有消费计划的 APIM，我非常希望有一个基于 IP 而不是基于 API 的速率限制器，就像消费计划的 APIM 一样。

我理解您需要根据 IP 基础限制请求的数量。如果是的话，我们有"IP 地址限制"的概念，可以限制来自 IP 地址的请求/ API 调用，正如在MS Doc的速率限制策略中所述的自定义基于密钥的限制。

注意：

是的，rate-limit-by-key 在 APIM 消费计划中不可用。

英文:

As @Silent mentioned, you can use rate-limiting policy in Azure APIM Consumption Plan.

You can import multiple Function APIS to the Azure APIM Service and can add the Rate-limiting policy to each API Level.
.NET 7 Azure Function 中的速率限制

> I have consumption plan APIM, and I’d very much like to have a IP based rate limiter instead of API based, like it is with consumption plan APIM

I understand that you need to limit the number of requests per IP basis. If yes and this is the scenario, we have “IP address throttling” concept to limit the requests/API Calls from the IP address as mentioned in this MS Doc of Custom key-based throttling in Rate-limiting policy.

Note:

Yes, the rate-limit-by-key is not available in APIM Consumption Plan.

答案2

得分: 1

以下是翻译好的部分：

"Just [ported ThrottlingTroll to Azure Functions][1] (.NET 7 Isolated).

Works as an Azure Functions Middleware.

Supports

  • [ingress throttling][2] (returning 429 TooManyRequests or impeding
    responses from HTTP-triggered functions),
  • [egress throttling][3] (an
    HttpClient that limits itself) and
  • propagating 429 TooManyRequests
    [from egress to ingress][4].

Configurable [via host.json, programmatically or dynamically (by periodically reloading rate limits from whatever external config store without restarting the service)][5].

Stores counters in memory [or in a distributed cache][6].

Install from NuGet:
dotnet add package ThrottlingTroll.AzureFunctions
and then configure like this:

  2.     workerAppBuilder.UseThrottlingTroll(hostBuilderContext, options =&gt;
  3.     {
  4.         options.Config = new ThrottlingTrollConfig
  5.         {
  6.             Rules = new[]
  7.             {
  8.                 new ThrottlingTrollRule
  9.                 {
  10.                     UriPattern = &quot;myfunction&quot;,
  12.                     LimitMethod = new FixedWindowRateLimitMethod
  13.                     {
  14.                         PermitLimit = 1,
  15.                         IntervalInSeconds = 5
  16.                     },
  18.                     // Identifying clients by their IP addresses
  19.                     IdentityIdExtractor = request =&gt;
  20.                     {
  21.                         request.Headers.TryGetValue(&quot;x-forwarded-for&quot;, out var clientIpAddress);
  22.                         return clientIpAddress;
  23.                     }
  24.                 }
  25.             }
  26.         };
  27.     });
  28. });
  29. ```"
  31.   [1]: https://github.com/scale-tone/ThrottlingTroll/tree/main/ThrottlingTroll.AzureFunctions#throttlingtrollazurefunctions
  32.   [2]: https://github.com/scale-tone/ThrottlingTroll/tree/main/ThrottlingTroll.AzureFunctions#how-to-use-for-ingress-throttling
  33.   [3]: https://github.com/scale-tone/ThrottlingTroll/tree/main/ThrottlingTroll.AzureFunctions#how-to-use-for-egress-throttling
  34.   [4]: https://github.com/scale-tone/ThrottlingTroll/tree/main/ThrottlingTroll.AzureFunctions#to-propagate-from-egress-to-ingress
  35.   [5]: https://github.com/scale-tone/ThrottlingTroll/tree/main/ThrottlingTroll.AzureFunctions#how-to-configure
  36.   [6]: https://github.com/scale-tone/ThrottlingTroll/tree/main/ThrottlingTroll.AzureFunctions#how-to-specify-a-rate-counter-store-to-be-used
  38. <details>
  39. <summary>英文:</summary>
  41. Just [ported ThrottlingTroll to Azure Functions][1] (.NET 7 Isolated).
  43. Works as an Azure Functions Middleware.
  45. Supports 
  47.  - [ingress throttling][2] (returning `429 TooManyRequests` or impeding
  48.    responses from HTTP-triggered functions),  
  49.  - [egress throttling][3] (an
  50.    HttpClient that limits itself) and  
  51.  - propagating `429 TooManyRequests`
  52.    [from egress to ingress][4].
  54. Configurable [via host.json, programmatically or dynamically (by periodically reloading rate limits from whatever external config store without restarting the service)][5].
  56. Stores counters in memory [or in a distributed cache][6].
  58. Install from NuGet:

dotnet add package ThrottlingTroll.AzureFunctions

  1. and then configure like this:

builder.ConfigureFunctionsWorkerDefaults((hostBuilderContext, workerAppBuilder) => {

  1. workerAppBuilder.UseThrottlingTroll(hostBuilderContext, options =&gt;
  2. {
  3.     options.Config = new ThrottlingTrollConfig
  4.     {
  5.         Rules = new[]
  6.         {
  7.             new ThrottlingTrollRule
  8.             {
  9.                 UriPattern = &quot;myfunction&quot;,
  11.                 LimitMethod = new FixedWindowRateLimitMethod
  12.                 {
  13.                     PermitLimit = 1,
  14.                     IntervalInSeconds = 5
  15.                 },
  17.                 // Identifying clients by their IP addresses
  18.                 IdentityIdExtractor = request =&gt;
  19.                 {
  20.                     request.Headers.TryGetValue(&quot;x-forwarded-for&quot;, out var clientIpAddress);
  21.                     return clientIpAddress;
  22.                 }
  23.             }
  24.         }
  25.     };
  26. });

});

  2.   [1]: https://github.com/scale-tone/ThrottlingTroll/tree/main/ThrottlingTroll.AzureFunctions#throttlingtrollazurefunctions
  3.   [2]: https://github.com/scale-tone/ThrottlingTroll/tree/main/ThrottlingTroll.AzureFunctions#how-to-use-for-ingress-throttling
  4.   [3]: https://github.com/scale-tone/ThrottlingTroll/tree/main/ThrottlingTroll.AzureFunctions#how-to-use-for-egress-throttling
  5.   [4]: https://github.com/scale-tone/ThrottlingTroll/tree/main/ThrottlingTroll.AzureFunctions#to-propagate-from-egress-to-ingress
  6.   [5]: https://github.com/scale-tone/ThrottlingTroll/tree/main/ThrottlingTroll.AzureFunctions#how-to-configure
  7.   [6]: https://github.com/scale-tone/ThrottlingTroll/tree/main/ThrottlingTroll.AzureFunctions#how-to-specify-a-rate-counter-store-to-be-used
  9. </details>

huangapple
  • 本文由 发表于 2023年2月14日 00:36:22
  • 转载请务必保留本文链接：https://go.coder-hub.com/75438732.html
  • .net-core
  • azure-functions
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定