Introduction
In this part of the series we'll explore limitations, quotas and pricing of the Data API itself.
Limitations with Data API in Amazon Aurora (Serverless v2)
Data API has the following limitations:
You can only execute Data API queries on writer instances in a DB cluster. However, writer instances can accept both write and read queries.
With Aurora global databases, you can enable Data API on both the primary and secondary DB clusters. However, a secondary cluster doesn't have a writer instance until it's promoted to be the primary. Data API requires access to the writer instance for query processing, even for read queries. As a result, read and write queries sent to the secondary cluster fail while it lacks a writer instance. Once a secondary cluster is promoted and has a writer instance available, Data API queries on that DB instance succeed.
Data API isn't supported on T DB instance classes.
For Aurora Serverless v2 and provisioned DB clusters, RDS Data API doesn't support some data types. For the list of supported types, see Comparison of RDS Data API with Serverless v2 and provisioned, and Aurora Serverless v1.
For Aurora PostgreSQL version 14 and higher databases, Data API only supports scram-sha-256 for password encryption.
The response size limit is 1 MiB. If the call returns more than 1 MiB of response data, the call is terminated.
The Data API size limit is 64 KB per row in the result set returned by the database. Make sure that each row in a result set is 64 KB or less.
Quotas of Data API in Amazon Aurora (Serverless v2)
Data API has the following service quotas (all of them are not adjustable).
| Quota name | Quota Description | Quota Value |
|---|---|---|
| Data API HTTP request body size | The maximum size allowed for the HTTP request body | 4 Megabytes |
| Data API maximum concurrent cluster-secret pairs | The maximum number of unique pairs of Aurora Serverless v1 DB clusters and secrets in concurrent Data API requests for this account in the current AWS Region | 30 |
| Data API maximum result set size | The maximum size of the database result set that can be returned by the Data API | 1 Megabytes |
| Data API maximum size of JSON response string | The maximum size of the simplified JSON response string returned by the RDS Data API | 10 Megabytes |
| Data API maximum requests | The maximum number of requests to the Data API | The max_connections value for Aurora Serverless v2 DB instances is based on the memory size derived from the maximum ACUs. However, when you specify a minimum capacity of 0.5 ACUs on PostgreSQL-compatible DB instances, the maximum value of max_connections is capped at 2,000, see Maximum connections for Aurora Serverless v2 |
Pricing of Data API
With Data API, you only pay when your API is in use. There are no minimum fees or upfront commitments. You pay only for the API and data requests your applications make. Data API request data payloads are metered at 32KB per request for data sent to the API or received from the API. If your API request data payload size is larger than 32KB, then for each 32KB increment there is a charge of one additional API request. So, if your payload is 35KB for example, you would be charged for two API requests.
Data API free tier includes one million API requests per month, aggregated across AWS Regions, for the first year.
Customers will also incur charges for AWS Secrets Manager and may also incur additional charges for AWS CloudTrail, if activated. Exact pricing depends on the region and can be seen Data API costs
At the time of writing the pricing in the us-east-1 region is as following:
| Number of Requests (per month) | Price (per million) |
|---|---|
| First 1 Billion requests | $0.35 |
| Above 1 Billion requests | $0.20 |
Conclusion
In this part of the series explored limitations, quotas and pricing of the Data API itself.
Sources:
Top comments (0)