A Day is A Very Long Time In Politics

To say Luxon stretched the truth is putting it mildly.

The Truth About AWS’s Auckland Data Centers: Launched, But Not as Promised

Based on the latest information as of September 3, 2025, Amazon Web Services (AWS) has indeed launched its Asia Pacific (New Zealand) Region, which went live on September 1, 2025. This is AWS’s first full cloud infrastructure region in New Zealand, consisting of three Availability Zones (AZs) in the greater Auckland area. The launch enables customers to run workloads and store data locally for better latency, data sovereignty, and compliance with New Zealand’s Privacy Act. However, the controversy you mentioned is spot-on: none of the originally promised data centers have been built by AWS itself. Instead of constructing its own facilities as announced in 2021, AWS appears to have pivoted to installing equipment (e.g., servers and racks) in third-party data centers, likely due to escalating power costs, construction delays, and environmental hurdles. This has led to accusations of overhyping the project, with Prime Minister Christopher Luxon’s endorsement of the launch drawing criticism for lacking substance.

The $7.5 billion NZD investment (over 15 years) and 1,000 annual jobs are still cited by AWS, but independent reporting suggests the actual build-out is far more modest—potentially just “a few racks” in existing facilities, creating far fewer jobs than promised. Below, I’ll break down the timeline, what happened, and the evidence.

Timeline of Announcements and Delays

AWS’s plans evolved amid challenges like stormwater consenting issues, a small site fire, wetland drainage controversies, and soaring electricity prices (which peaked at NZ$900/MWh in 2024). Here’s a chronological overview:

What Was Built vs. What Was Promised

• Promised (2021): Three physically separate AZs (each with one or more data centers) built by AWS in Auckland, totaling hyperscale facilities for high availability, fault tolerance, and data residency. Full ownership for security and resilience, powered by renewables.
• Reality (2025 Launch): The region is operational, but AWS hasn’t built any data centers. Instead:
  • Equipment installed in existing third-party sites (e.g., CDC in Hobsonville or Silverdale, or DCI/Microsoft facilities in northwest Auckland).
  • This is more like an “Outpost” or edge deployment—racks of servers in colocation spaces—rather than dedicated hyperscale builds. Experts like Catalyst IT’s Peter Christie call it “less robust” for New Zealand’s seismic risks and question the resilience.
  • No new construction: The west Auckland site (purchased for NZ$33 million) is abandoned after earthworks; environmental damage (e.g., drained wetlands) remains unaddressed.
  • Power: Still 100% renewable via Mercury PPA, but drawn from the grid rather than dedicated on-site generation. High prices (up due to shortages) likely killed the build.

AWS maintains secrecy on locations for “security reasons,” but consenting documents and property records confirm the west Auckland focus. The pivot allows the region to launch without further delays, but it falls short of the “world-class infrastructure” hype.

Evidence from Sources

• Official AWS Statements: AWS blogs and press releases (e.g., September 1 announcement) confirm the launch and benefits like reduced latency (from Sydney’s ~40ms to single-digit ms for Auckland users). They list 20+ early customers (e.g., Ministry of Transport, New Zealand Post) and reaffirm the investment. However, they avoid specifics on construction, stating: “We found a way to establish the region” (AWS NZ Manager Manuel Bohnet).
• Critical Reporting:
  • Newsroom (September 2, 2025): Investigative piece by Jonathan Milne details the abortion of plans, citing insiders and documents. AWS spent millions but halted due to costs; now renting space. Environmental fallout: Site cleared but unused.
  • Data Center Dynamics (DCD, May 2025 & September 2025): Confirms stall from stormwater/fire issues; launch uses existing infra.
  • RNZ & NZ Herald (September 2, 2025): Luxon’s hype called “embarrassing”; site “sits bare” despite event.
• Social Media (X/Twitter): Semantic and keyword searches show backlash since September 1:
  • Users like @JonoMilne (Newsroom editor) and @nicholasphilp call it a “fiasco” and “no $7.5B spend.”
  • Posts from @GayMaxine, @themblogger31, and @SolidAirJohn highlight “no data centres built” and wetland damage.
  • No pro-AWS counter-narratives in recent posts; focus on skepticism (e.g., “Luxon drunk on the Kool-Aid”).
• Economic Impact: AWS claims NZ$10.8 billion GDP boost and 1,000 jobs (e.g., maintenance, engineering). But critics argue renting space means fewer direct jobs (dozens, not thousands) and diluted investment.

Implications and Broader Context

• For Users: The region works—customers like One NZ report low-latency AI/ML benefits. Data sovereignty is met, though resilience may be lower without dedicated AZs.
• Environmental/Social: Drained wetlands and a fire raised concerns; AWS’s “water positive by 2030” goal is global, but local impacts linger. High power use (undisclosed, but hyperscale centers consume MWs) strains NZ’s grid amid shortages.
• Political Angle: Luxon’s involvement (e.g., at Cloud Day) ties to economic wins, but it’s seen as recycled 2021 news. Opposition (e.g., NZTech CEO Graeme Muller) praises skills training (50,000+ trained via AWS Academy), but questions the “investment.”
• Comparisons: Microsoft launched its NZ region in late 2024 (also Auckland-based, 100% renewable via geothermal). Google and locals like Spark/Datacom are expanding, but AWS’s pivot highlights industry challenges in NZ (power costs, consents).

In summary, the AWS region is “online” and functional today, fulfilling basic promises for cloud services. But the “built” data centers? Not by AWS—construction was abandoned, leaving a controversial, half-finished site and a scaled-back rollout. This discrepancy explains the “not even built” comments, likely from recent exposés. For official details, check AWS’s global infrastructure page; for migration, customers can use the AWS Console. If you’re a user or investor, consult AWS directly for specifics.