Loading today’s stories
Build1 distinct publisher3 min readUpdated
AWS cut Glue pricing 30% and shipped full Iceberg v3, but the rate follows the version string, and its own two announcement posts do not agree on which Python you will be running.
The Engineer · Build desk
Compiled by The EngineerSomething wrong?How this is made
The 30% is attached to a version, not to an account. AWS describes it as 30% lower pricing than previous Glue versions [1], which means the saving lands on jobs that have actually been moved to 6.0 and on nothing else. Run the arithmetic the other way and it is a compute budget story: at 70% of the old rate, the same monthly spend buys roughly 43% more Glue capacity [19]. That is the size of the prize for finishing a migration, and it is the size of the money left on the table for every pipeline that stays where it is.
The bill is legible from AWS's own tooling. Glue 6.0 moves the runtime to Apache Spark 4.1, Python 3.12 and Scala 2.13 [2], and AWS ships a Spark Upgrade Agent plus an auto-upgrade option for existing jobs [13] alongside a dedicated migration guide for getting Spark jobs onto version 6.0 [14]. Vendors do not write migration guides for parameter flips. Note also what the reassurance covers: the "no API changes are required" line is about selecting the version through the existing `--glue-version` parameter on `create-job` and `update-job` [12], which is the control plane. It says nothing about the dependencies compiled into your job.
Which matters, because the two AWS posts announcing the same release do not agree on the interpreter. The launch blog says Python 3.12 [2]; the What's New entry says Python 3.13 [3]. One of those is wrong, and a one-minor-version gap is the difference between a wheel that loads and a wheel that does not [4]. The streaming numbers diverge too: the blog promises single-digit millisecond latency for stateless streaming [9], the What's New post says sub-second [10], and the published upper bounds sit more than 100x apart [11]. The feature lists are also asymmetric, with nanosecond-precision timestamps appearing only in the blog and deletion vectors and DEFAULT column values only in the What's New entry [20]. Pin your version matrix off the runtime, not off either page.
On the build-versus-buy side, the interesting item is not the price. It is VARIANT with shredding, which AWS says lets you store and query JSON, logs and event data without flattening schemas, removing duplicate copies and custom parsing code [5]. If that holds under load, the thing you delete is an entire stage of hand-written pipeline plus the breakage that follows an upstream schema change, and that is the part of a self-managed lakehouse that costs staff time rather than instance hours. Geometry and geography types and nanosecond timestamps remove two more categories of workaround [7].
Treat the superlative with more care. AWS claims the most complete Iceberg v3 implementation on any fully serverless managed Spark service [6], and the qualifier does the work: the comparison set excludes anything you run yourself. The spec support is upstream, in Iceberg 1.11.0, which Glue 6.0 is built on [5]. What AWS is selling here is the packaging and the 30%, and the packaging is the part you cannot get by upgrading a library.
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
AWS announced general availability of AWS Glue 6.0, delivering 30% lower pricing than previous AWS Glue versions and full support for Apache Iceberg v3 features.
Glue 6.0 delivers the complete Apache Iceberg v3 specification built on Iceberg 1.11.0, with the VARIANT data type and shredding support as headline feature, allowing JSON, logs and event data to be stored and queried without flattening schemas and eliminating duplicate data copies, custom parsing code and pipeline breakage on schema change.
Additional Iceberg v3 capabilities in Glue 6.0 include geometry and geography data types for native spatial processing, nanosecond-precision timestamps, and unknown type handling for evolving schemas.
The What's New post lists deletion vectors for row-level updates and DEFAULT column values among the Iceberg v3 additions, and says Glue 6.0 also includes newer versions of Apache Hudi and Delta Lake.
Existing jobs can be upgraded to Glue 6.0 using the Spark Upgrade Agent in AWS Glue Studio or an auto-upgrade feature on existing Glue jobs.
AWS documentation includes a dedicated guide, Migrating AWS Glue for Spark jobs to AWS Glue version 6.0.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
First-party and specific, but self-inconsistent and unverified
The cluster contains two primary-source AWS announcements that are concrete about version numbers, pricing direction, migration mechanics and region coverage — strong evidence that the release and the 30% rate exist. It contains no independent testing, no benchmark, and no third-party publisher, and the two posts contradict each other on the Python minor version and on the streaming latency bound, which caps how much of the technical detail can be treated as settled.
Generally available everywhere, no observed uptake
Supply-side adoption signals are maximal for day one: GA across all Commercial, GovCloud (US) and China regions, a version-string switch with no API changes, and vendor migration tooling. Demand-side signals are absent — the sources disclose no customers, no job counts, no migration volume and no usage data — so measured adoption reflects availability only, not observed use.
Claims run ahead of the published evidence
The pricing and availability claims are plain and well-supported, so this is not pure hype. But the release is sold with an unverifiable superlative ('most complete Iceberg v3 implementation on any fully serverless managed Spark service'), a single-digit-millisecond latency figure that AWS's other post downgrades to sub-second, unquantified 'faster performance' assertions, and a 'no API changes required' frame that understates a major Spark 4.1 runtime migration. Overstatement is concentrated in performance and competitive positioning rather than in the commercial facts.
Entirely vendor-authored promotional material
Every source is AWS publishing about its own paid service through channels designed to drive adoption: a launch blog and a What's New entry, both closing with calls to try the console and links to the pricing page. The 30% reduction is itself an incentive instrument — it is gated on the new version, so it pushes customers to migrate onto the runtime AWS wants to operate, and the disclosure omits deprecation timelines and rate tables that would let customers evaluate the trade independently.
Commercial facts solid, technical detail shaky, single publisher
Confidence is high that Glue 6.0 shipped generally available at a 30% lower rate with Iceberg v3 support and all-region coverage, because that is stated consistently by the operator of the service. It is materially lower on runtime specifics and performance, because the cluster has one publisher, no independent verification, and two internal contradictions (Python version, streaming latency) plus divergent feature lists in the same 24-hour window.
build
Iceberg votes to forbid new equality deletes in V4, and Parquet 1.18.0 lands with two corruption bugs1 distinct publisher
product
Cloudera bets the agentic AI bottleneck is where the data sits, not which model runs1 distinct publisher
build
S3 annotations move the label without moving the bytes, and checksums cannot see it1 distinct publisher
build
Force the tool call, then hand Lightsail a long-lived key1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
2 articles · August 21, 2026