For years, Amazon has been the quiet giant of the data center boom, striking deals behind closed doors, signing paperwork that kept public officials silent, and showing up in communities with dump trucks, cranes, and a tight-lipped legal team. But last week, the company signaled something of a turn, and it read less like a corporate victory lap and more like a carefully worded attempt to make amends. In a blog post published Friday, Amazon CEO Matt Garman announced that the company no longer uses nondisclosure agreements in its arrangements with county officials—an official acknowledgment of a practice that had become one of the most bitter flashpoints in the country’s data center expansion. Alongside that pledge, Garman promised that $1 billion would be invested over the next five years in communities that host the company’s data centers. That money, he said, would go toward free community college programs, workforce training, and energy efficiency upgrades for schools, homes, and community buildings. For a company that helped perfect the art of the mystery deal, this was as close to a public apology as corporate America usually gets. The message seemed to be: we heard you, we need you, and we’re at least willing to stop hiding the details. Whether it will be enough to cool the anger brewing in data center towns across the country is another question, but it is a notable shift from the era when Amazon’s name itself was treated like a classified secret.
The money, of course, is not merely a charitable gesture. It is aimed directly at the most obvious grievance that local communities have raised as giant warehouses of blinking servers have multiplied: they were being asked to provide land, power, and water for facilities that felt more like black boxes than good neighbors. By promising that $1 billion over five years will fund free community college programs, workforce training, and energy-efficiency retrofits for schools, homes, and community buildings, Amazon is trying to make its presence feel less like extraction and more like partnership. For a high school senior in a rural county outside Columbus, Ohio, or in a small parish in Louisiana, this might mean an associate degree without debt, or a certification that lets them work on the very electrical grids these data centers are straining. For a town whose public school boiler is older than the internet, it could mean heating bills drop for good. The humanizing effect is intentional: Amazon wants residents to think of its data centers not as mysterious concrete fortresses, but as anchors for local mobility and resilience. Still, $1 billion over five years, spread across the many communities Amazon has built or is building, is a relatively small price tag compared with the billions Amazon has poured into individual campuses. Garman’s post framed the spending as an acknowledgment of the ‘right’ role for corporate neighbors, but the skeptical reading is just as obvious: Amazon is trying to buy breathing room while it builds artificially intelligence infrastructure at breakneck speed. The company knows that the towns accepting these facilities are the ones that ultimately green-light the next generation of AI data centers, and it needs them to say yes with their eyes open—or at least with less reason to say no.
Amazon’s timing is no accident. The AI buildout has hit a wall of local resistance, and Garman conceded clearly in the blog post that the backlash is real enough to threaten the entire national project. “Right now there are over 100 data center moratoriums being considered across the country,” he wrote. “If these measures are enacted, the U.S. could be writing its own losing ticket to the race, and the consequences would last generations. As a country, we can’t afford to find ourselves in that position.” That is typical CEO rhetoric—grand, urgent, tinged with the language of national destiny. But it also reflects an uncomfortable truth that many local officials have been saying for years: data centers have grown so large, so hungry for electricity and water, that ordinary municipal review processes are struggling to keep up. Towns that welcomed a single “server farm” in the 2010s now find themselves facing sprawling campuses the size of small cities, consuming as much power as neighborhoods, churning out heat, noise, and a confusing mix of construction dust and traffic. Moratoriums are the natural response—a way to say “not so fast” while laws catch up and costs are understood. Garman’s warning is directed at undecided local boards, but it is also aimed at Congress, state governors, and anyone who thinks the AI boom can simply be paused without consequences. He is arguing that data centers are infrastructure for the future,just as highways and airports were in earlier generations. The problem is that past infrastructure projects were built with public debate, visible plans, and shared sacrifice; data centers have too often been built with secrecy, tax breaks, and little accountability. The $1 billion and NDA pledge are attempts to close that gap, but they do not erase the fact that Amazon helped create the problem in the first place.
The nondisclosure agreement fight sits at the heart of this whole controversy. When a county official signs an NDA with a data center developer, that official is effectively barred from telling constituents basic facts about the project—how much energy it will consume, how much water it will draw, how many construction jobs it will create, even sometimes which tech company is actually behind the development. That last point deserves a moment of reflection: an elected county commissioner, paid by public taxes, could know exactly what hyperscaler is moving in and yet be legally prohibited from saying the name aloud to the people who voted them into office. Residents would see towering cranes and excavation pits, but county staff would have to say “we can’t discuss that.” In July, the New York Times reported that secret agreements at all levels of government were crucial in building out plans for Hyperion, its massive data center in Louisiana—a project that was shaping up to be one of the most consequential in the state’s history, yet was surrounded by so many confidentiality clauses that public officials themselves appeared unsure what they were allowed to reveal. For many people, this was less “economic development” and more “shadow government.” It was no wonder that data center moratoriums were popping up like weeds; voters do not revolt against the construction noise alone, they revolt against being treated like outsiders in their own communities. Amazon’s promise to stop using NDAs with county officials is therefore not just a legal tweak; it is an admission that secrecy had become politically toxic.
Lawmakers have responded to that toxicity with unusual speed and bipartisan energy. In recent months, Pennsylvania Governor Josh Shapiro, Massachusetts Governor Maura Healey, and Delaware Governor Matt Meyer have all cracked down on data center NDAs through executive orders, making clear that public officials should not be signing away their right to communicate with their own constituents. Multiple states, including New York, New Jersey, Indiana, and Ohio, have considered legislation that would ban the practice outright. At the federal level, a bipartisan group of lawmakers recently introduced the “No Secrets for Data Centers Act” in the House, a bill whose name is memorable precisely because it captures the frustration that local officials have been voicing for years. Earlier this week, Representative Jamie Raskin, a Maryland Democrat and one of the bill’s sponsors, sent letters to Amazon, Google, Meta, and Oracle demanding detailed information about their use of data center nondisclosure agreements. The letters were a shot across the bow: Congress is not content to let secrecy lives in the gray zone of local economic developmentany longer. Amazon, notably, told the Wall Street Journalthat it was already no longer using NDAs—a response that made it seem almost eager to be seen as cooperative. Google, Meta, and Oracle apparently did not return the Journal’s request for comment, which itself says something about how slowly the culture is changing. The bill may or may not become law, but it has already changed the conversation: what was once accepted practice is now a political liability, and companies that continue to demand confidentiality are increasingly being asked by lawmakers, journalists, and angry residents to explain exactly what they are trying to hide.
Amazon has been at the center of some of the most high-profile examples of that culture, which is why this latest announcement feels both overdue and carefully calibrated. In Tucson, Arizona, Amazon was revealed last year to be the tenant of a controversial data center project—and that revelation came only through a public records request from a local outlet, because the NDA in place barred county officials from sharing the identity of the end tenant. Imagine living in a neighborhood being transformed by construction crews, wondering whether the project will bring jobs or just traffic, and not even being allowed to know which company is responsible. Amazon has since exited that project, but the damage to its reputation had already been done. In South Bend, Indiana, where Amazon has invested more than $13 billion into a massive data center campus, some elected officials have publicly claimedthat local government employees were unable to answer basic questions about the project because they had signed NDAs with the company. That is not a small allegation: it suggests that the people responsible for representing taxpayers felt their hands tied by a private corporation. For Amazon, dropping NDAs is therefore a meaningful step, but it does not automatically undo the years of suspicion built up by these episodes. It also does not fully answer the harder questions lurking beneath the debate: should data centers be required to help pay for the grid upgrades they demand? Where will water come from in drought-prone regions? What obligations do these facilities have to local housing markets, school systems, and emergency services? Garman’s pledge of $1 billion over five years is a good start, but it is a relatively modest offer compared with the scale of the infrastructure boom that is underway. The real test will be whether Amazon speaks plainly not just in blog posts, but in county hearing rooms, city council meetings, and community forums—long after the cameras are gone and the promise is forgotten. Secrecy was never just a legal technicality; it was a signal that told communities they were temporary hosts to a distant machine. By abandoning that signal, Amazon has opened the door to a more honest conversation. Whether it is ready to have that conversation, with real give-and-take rather than press release generosity, remains the open question. It is a step, not a solution—but in a world full of broken data center promises, at least it is a step in the right direction.
