👀 Views: 1963 💬 Answers: 1 📅 Created: 2025-06-10

oci api-gateway rate-limiting json

I've searched everywhere and can't find a clear answer. I'm encountering an issue with the OCI API Gateway where the rate limiting seems to be ineffective. I set up a policy for throttling requests to limit each client to 100 requests per minute. However, during testing, I noticed that multiple clients can send requests concurrently without being throttled, which defeats the purpose of the rate limiting. I configured the rate limiting in my API Gateway with the following settings: ```json { "rateLimit": { "requestsPerMinute": 100, "burstCapacity": 10 } } ``` While testing, I utilized a load testing tool to simulate requests from 10 different clients. The tool successfully sent 200 requests per minute, and I expected the API Gateway to return a `429 Too Many Requests` status after the first 100 requests. Instead, every request was processed successfully, which is concerning. I verified that the API Gateway deployment was using the correct configuration, and I even tried redeploying it multiple times to ensure there were no caching issues. Additionally, I checked the metrics on the gateway, and it did not show any rate limiting being enforced during the test period. I’m using the OCI API Gateway version 1.0.12 and have set the rate limiting policy under "Rate Limiting" in the API settings within the OCI console. I also examined the documentation to confirm that I had implemented the settings correctly. Can anyone shed light on why the rate limiting is not applying as expected? Are there any additional configurations needed, or is this a known issue? Any suggestions on how to effectively troubleshoot this would be greatly appreciated! I'm working on a service that needs to handle this. Any ideas what could be causing this?