CONNECTED RESEARCH

Knowledge map

Explore research through connected companies, technologies and questions. Every relationship links to its evidence.

55 / 55 articles with reviewed reader guides · 202 reviewed relationships

Amazon RDS Data API response-size limits

Amazon RDS Data API response-size limitsAmazon RDS Data API responseRow-based paginationRow-based paginationLatest 20 complete research recordsLatest 20 complete research

Select a connected node to continue exploring. Open the evidence below to distinguish reporting, analysis and hypotheses.

Article analysis

Amazon RDS Data API response-size limits → constrains → Row-based pagination

Row pagination does not guarantee compliance with byte limits when an individual record contains large audit JSON; both the per-row and total-response limits must be considered.

Read the evidence
Ordinary row-based pagination can reduce the response size of many lists, but if a row contains very large audit JSON, even LIMIT 1 cannot guarantee that a single response is safe. AWS also separately describes a 64 KB per-row limit, so both individual rows and the total response should be considered.

Background sources for the article's reasoning: [S4] Amazon Web Services

Read the full research

Reported evidence

Amazon RDS Data API response-size limits → constrains → Latest 20 complete research records

The incident was traced to the research query’s response size: the JSON for just 20 complete records measured 1,094,895 bytes, exceeding the documented 1 MiB result-set limit.

Read the evidence
Production logs located the problem in the research-list query and the Aurora Data API response-size limit. The query JSON for the latest 20 complete research records totaled 1,094,895 bytes, with the continually growing database-wide deduplication audit material increasing the size of individual records.

[S1] Aperture Intelligence [S4] Amazon Web Services

Read the full research

Connected research

cloud

Aurora Data API Responses Exceeding 1 MiB Cause Admin 502 Errors: Our Reproduction and Chunked-Read Fix

Why did Aperture’s research list return 502 after successful login, and how can oversized records be read without losing audit evidence or mixing snapshots?

A measured incident review with an implementation using 8,192-character chunks, at most eight chunks per call, a row-and-chunk cursor, and a caller-managed Repeatable Read transaction. It also provides PostgreSQL regression tests and separate production browser verification.