InfoQ's October 17 recap is an August deal and a September Aurora feature

A headline that bundles two older documents

InfoQ's October 17, 2026 story carries a headline about Amazon, DuckLabs, and DuckDB inside Aurora PostgreSQL. The body is a recap of two earlier company documents, not a deal signed that morning. One document is the acquisition of DuckLabs. InfoQ says the open-source DuckDB project stays under the MIT license at the independent DuckDB Foundation, and that AWS did not buy the project itself. The other document is a feature, dated in that recap to September 30, in which Aurora PostgreSQL can query Iceberg and Parquet files in S3, including S3 Tables, and can see live uncommitted writes. The recap names aurora_analytics, Aurora PostgreSQL 17.11 and newer and 18.6 and newer, commercial regions, GovCloud, and no extra charge beyond Aurora compute and the S3 requests. duckdb.org is the project. The Aurora product page is the database. Neither of those two homepages is the September note. The distributed-cloud desk isDistributed Cloud.

A company and a project are different nouns

Buying DuckLabs, on InfoQ's telling, buys a team and a business. It does not, on that telling, transfer the MIT project into AWS. Readers who hear Amazon acquired DuckDB have collapsed the noun. The foundation remaining the steward of the license is the sentence that prevents the collapse. Amsterdam remaining the team's base, and the existing technical leads remaining the technical leads, are the sentences InfoQ uses to say the project's direction was not moved to Seattle as part of the close. The paper isFutureweb.

A query path is not a migration

The Aurora feature, as recapped, lets a PostgreSQL engine read columnar files in S3 without a separate product charge. That is a connector story: the bytes can stay in the bucket, and the database can still see them, including writes that are not committed yet. It is not a statement that every warehouse has moved, or that DuckDB replaced PostgreSQL. The versions InfoQ names are the gate. A cluster below those versions is outside the sentence. Software isSoftware.

Why the October date still matters

A recap is news when a large audience meets the two documents for the first time under one headline. It is not news in the sense of a new contract. This page uses October 17 as the day InfoQ published, and August and September 30 as the days the recap assigns to the events. Mixing them would make a six-week-old feature look like a same-day launch. GovCloud being on the list is a scope sentence worth keeping, because a feature that is only in commercial regions would be a different announcement. Hardware isHardware.

Who is in scope

Aurora PostgreSQL customers on the versions InfoQ names, in the regions it names, are the feature's audience. DuckDB users who ship the MIT project are the audience of the license sentence, and InfoQ says that audience did not get a new owner. People reading only the headline are the audience this brief is for, because the headline is what collapses the two events. Security isSecurity.

What this page did not open

The primary company posts are older than InfoQ. This brief's narrative source for the close and the feature is InfoQ's recap of them. duckdb.org and the Aurora product page identify the project and the database. They are not substitutes for the September engineering post. Where a detail is only in InfoQ, it is labeled as the recap. A second lab's benchmark is a different kind of claim and is not involved here. An evaluation standard on this paper isan evaluation a second lab can run.

What this page will not say

This page will not say Amazon owns DuckDB. It will not say the feature shipped on October 17. It will not print a connection string. The record is a company acquisition that left a foundation in place, and a database feature that reads a lake, both older than the magazine date, both public again because InfoQ put them in one story. Networking is Asked directly, Did Amazon acquire the DuckDB open-source project? InfoQ's recap says Amazon acquired DuckLabs, the company, and that the DuckDB project remains MIT-licensed under the DuckDB Foundation. AWS is not described as the new owner of the project. duckdb.org is the project home. It is not the acquisition contract.Networking.

A lake query and an agent block

Another page today is about sites that refuse an automated client. This page is about a database that is willing to read files in a bucket. Both are questions of who may touch bytes that live somewhere else. They are not the same mechanism. The agent page is about a booking desk and two banks. This page is about Aurora and DuckDB. Privacy isPrivacy.

Where the recap sits

InfoQ is the recap. duckdb.org is the project. The Aurora page is the product. Nothing here is a claim that this desk re-read the September engineering post line by line. The short answer this page will stand on is this: InfoQ recaps a completed acquisition of DuckLabs, the company, while saying the DuckDB project stays MIT-licensed under the independent DuckDB Foundation and that AWS did not acquire the open-source project. It also recaps a September Aurora PostgreSQL feature that queries Iceberg and Parquet in S3, including S3 Tables, without a separate charge beyond Aurora compute and S3 requests. The headline is October 17. The events it bundles are earlier.