everyone
I'm using Amazons API Gateway as a proxy for Dynamo DB. I've read through the documentation but I can't seem to find a lot of information about how to get the next set of items in a collection.
The documentation says that api gateway only returns 25 items at a time. I see under the api gateway documentation that it has a "next" call but I'm not sure how to use it.
For example, if i have an api such as apiurl.com/videos/1 which references to the videos for a specified user ID how do i get the next set of videos in the collection.
This is my first time building an api or implementing a backend so it's a little confusing.
Thanks ahead of time!
Please review this detailed blog post which answers your exact question:
https://aws.amazon.com/blogs/compute/using-amazon-api-gateway-as-a-proxy-for-dynamodb/
Regarding the 25 item/request limit - this limit is imposed on items returned from API Gateway's management APIs. The limits imposed on APIs that you run on API Gateway itself (like your DynamoDB proxy API) have a separate set of limits. See this document for more details on both classes of limits. Additionally, DynamoDB itself will have limits on its APIs, such as 100 items per BatchGetItem and 1 MB per Query or Scan, that you will also have to take into consideration.
Related
On every request to the API backend, we can have the API key from the gateway, but if we need to perform operations based on the usage plan, then we also need the usage plan information. One of the use cases is to provide limited services for the FREE plan.
We can determine the usage plan based on the provided API key with the help of the AWS SDK, but it will add additional latency to the API responses. Is there a better way to achieve this, perhaps through the gateway settings?
If the usage plan information can be passed as a header or query string to the backend, that would be great!
Can I limit my API Gateway request limitation?
For example
URL A with path like this :
aaaaaaaa.com/predict
I set URL A only can be requested 1000 per day and the same URL with another path like this :
aaaaaaaa.com/calling
/calling only can be requested 500 per day
So, can I set a path with a limited request?
I wrote an article with Cloud Endpoint and it's the same thing with API Gateway (simply a managed version of Cloud Endpoint).
If you want to limit the requests per day AND per requester, you need to add API keys to differentiate all the requesters. And the requester need to use it to indicate in which quota the request if counted.
Take care, an API identify a project. If you have several requesters, you need several API keys, each one in a different project. Else, if you put all in the same project, it's the same project which will be identified, and thus the same quota decreased.
I’m building a service and I’m planning to charge a fixed price for each lambda call.
How to count requests per client if the lambda function being called is the same? I’m planning to pass a client id
You can use API Gateway Usage Plans for your requirement.
After you create, test, and deploy your APIs, you can use API Gateway usage plans to make them available as product offerings for your customers. You can configure usage plans and API keys to allow customers to access selected APIs at agreed-upon request rates and quotas that meet their business requirements and budget constraints. If desired, you can set default method-level throttling limits for an API or set throttling limits for individual API methods.
A usage plan specifies who can access one or more deployed API stages and methods—and also how much and how fast they can access them. The plan uses API keys to identify API clients and meters access to the associated API stages for each key. It also lets you configure throttling limits and quota limits that are enforced on individual client API keys.
Read this docs for more detail explanation.
You can use api gateway https://aws.amazon.com/api-gateway/
"Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale. APIs act as the "front door" for applications to access data, business logic, or functionality from your backend services."
It provides you with statistics about usage as well as different options like limit numbers of requests per api_key, etc
I'm using AWS API Gateway with quota and need increase the number of requests made to api only if my backend return response with status code 200. So, responses with status different of 200 not are accounted for quota usage.
It's possible? If not, how i could make this?
Thanks
Recently i faced the same question, my solution is a little workaround.
You create two apis with aws api gateway and also two usage plans. The first api should be the api used by your customer, the second api exists only to increase the quota usage value for an API Key, so it should be a simple POST Endpoint. Now create one free usage plan (only throttling) and one usage plan with quota limitation enabled. Then connect the free plan to your api which is responsible for processing the data and connect the quota plan to the additional quota api.
Finally create an API Key for your customer, add both usage plans. Now you only need to call your quota api with the API Key provided by your customers, when their requests were successfully.
Hope this will work for you aswell.
I would like to have a policy on an API Gateway that would throttle requests based on a header value. For example, header value "AAA" would be allowed up to 10 requests per day, "BBB", 20 requests. Is this possible? How can I achieve this? Note: I am trying to avoid writing a lambda function for this purpose, because then I would need to keep state, etc.
API Gateway has Usage Plans, which support what you are attempting to do.
Each usage plan can have a throttling limit, which restricts requests per second and burst rate. Usage plans can also have quotas, which would allow you to add limits on requests per day.
API Gateway allows you to add API Keys to a usage plan. API Keys are sent HTTP header (x-api-key).
You can find more details in the Usage Plans for API Gateway launch blog and API Gateway Usage Plan docs.