OCI API Gateway Rate Limiting optimization guide as Expected with Python Lambda Function
I'm currently working on an OCI API Gateway that invokes a Python Lambda function. I have configured rate limiting on my API Gateway to allow a maximum of 100 requests per minute, but it seems like the limit isn't being enforced correctly. I've noticed that my Lambda function is being invoked over 200 times in a minute when I send multiple requests. Here is how I set up the API Gateway configuration: ```json { "rateLimits": { "maxRequestsPerUnit": 100, "unit": "MINUTE" }, "backend": { "type": "FUNCTION", "functionId": "ocid1.fnfunc..." } } ``` I tested this by sending a burst of requests using a simple Python script: ```python import requests import time url = 'https://my-api-gateway-url/endpoint' for _ in range(200): response = requests.get(url) print(response.status_code) time.sleep(0.1) # 10 requests per second ``` Despite the rate limit configuration, I'm seeing successful responses (200 OK) from the Lambda function well beyond the specified limit. I have double-checked my IAM policies and ensured that the API Gateway has the required permissions to invoke the function. Additionally, I've confirmed that the API Gateway is correctly set to use the rate limiting configuration. Is there something that I might be missing in the configuration, or is there a known scenario with the rate limiting feature in OCI API Gateway? Any guidance on how to troubleshoot or enforce the rate limiting correctly would be greatly appreciated.