Serverless APIM

Question

The serverless APIM is giving 429 error due to limit exceed. Do we have to upgrade the APIM to standard SKU. We do not have any policies to rate limit the APIs.

Answer 1

Hi Dal ,

If you're encountering 429 errors in serverless Azure API Management (APIM) due to rate limit exceeded and you don't have explicit rate-limiting policies, upgrading to the standard SKU might be necessary. The serverless SKU has certain limitations, and the standard SKU provides more flexibility in terms of scalability and rate limiting. Evaluate your API traffic patterns, and if the demand exceeds the serverless SKU limits, upgrading to standard SKU could resolve the issue.

Regards, Saravanan Ganesan.

Answer 2

@Dal Ram Thanks for reaching out.

Without the proper analysis of the root cause of the 429 error it would be difficult to confirm if migrating to Standard SKU will resolve the issue.

Generally, when you receive the HTTP status code 429 it means too many requests. But you need to first validate if the 429 error is from APIM or your backend API call.

You mentioned that you do not have any policies to rate limit the APIs. It is possible that your APIs are being called too frequently or by too many clients, which is causing the limit to be exceeded. You may want to consider implementing rate limiting policies to control the traffic to your APIs.

If you are still unsure about the cause of the issue, you can try to analyze the logs and metrics for your APIs to identify any patterns or anomalies. This may help you to pinpoint the root cause of the issue and take appropriate action.

Let me know if you have any queries or concerns.

Please 'Accept Answer' if it helped so that it can help others in the community looking for help on similar topics.