For years, the first document many towns saw when Amazon came calling about a data center was a contract that told local officials to stay quiet. That requirement is ending.
Amazon said on October 11 that it will no longer ask local governments to sign confidentiality agreements while negotiating data-center projects, a change the company confirmed to TechCrunch. Microsoft made the same commitment earlier this year, which makes Amazon the second large cloud provider to give up a tool it had used to keep early talks out of public view.
Matt Garman, the chief executive of Amazon Web Services, had already put the change into a company blog post responding to community complaints. In it, he said the company has invested more than $1 billion over the past three years in the U.S. communities where its data centers are built.
The figure is aimed at critics who say the sites draw heavily on local power and water, add strain to electric grids and deliver less to a town than the promises made during negotiations. Those critics have grown more numerous as the buildout has accelerated, and they have begun to organize.
Opposition has produced more than a hundred proposals to pause or restrict data-center construction, reaching from New York to San Francisco. The measures take different forms, including building moratoriums, zoning changes and new utility rules, but they share a single demand: that residents learn what a project will cost their community before officials approve it.
One detail keeps those fights alive regardless of the outcome. Many of the pauses are written to lapse after a set number of years, and that window often closes before the construction cycle of a large data center has run its course, a cycle that typically takes two to five years. A restriction passed in one budget year can be gone before the site is finished. The result is a vote that feels decisive and a project that proceeds anyway.
The confidentiality agreement was never about secrecy for its own sake. It allowed a company to share load projections, water consumption figures and tax terms with a handful of officials without handing the same numbers to competitors or to the press. It also meant those officials could not discuss the deal with the people who would live beside it, a trade many towns have decided they no longer want to make.
Microsoft’s earlier decision set the precedent, and Amazon’s move shows the practice is retreating across the industry rather than at a single company. The reason is political as much as ethical. Every confidentiality agreement that becomes public becomes an argument for the opposition: evidence that the town was kept in the dark while a project’s terms were settled.
Giving up the agreements does not resolve the disputes underneath them. The questions that fill public hearings, including how much water a campus will use, how large a tax abatement it will receive and who pays for grid upgrades, remain open, and a company that discusses them openly still has to win a vote.
The change is also voluntary. No regulator required it, and nothing binds the next company that arrives in a town with a proposal and a preference for quiet. A pledge from two of the largest buyers of land and power in the country carries weight because of their scale, not because of any enforcement behind it.
For the cloud companies, the calculation is straightforward. The buildout depends on local consent, and consent is getting harder to obtain. Approvals, power connections and land deals all move through the same town councils and county boards that opposition groups have learned to target, which turns a public-relations problem into a construction schedule problem.
Data centers have become one of the largest categories of private construction in the United States, and the pace has brought a new kind of local politics to towns with little experience of it. A single campus can consume as much electricity as a small city and take years to build, which means the decisions are made in public whether or not the negotiations are.
Amazon’s own numbers suggest the stakes. More than $1 billion in community investment over three years is a small fraction of what the company spends on the buildings themselves, and it is offered in part as evidence that the trade is worth making. Whether residents accept that evidence is something the company now has to argue in the open.
Both companies have framed the change as a response to feedback rather than a retreat. Garman’s blog post, which came before the formal confirmation, described the company’s engagement with communities as an ongoing effort. The timing, after Microsoft’s pledge and in the middle of a wave of local restrictions, suggests the industry has concluded that the old approach now costs more than it saves.
The unresolved question is what replaces the agreements. Transparency is a precondition for a real negotiation, not the negotiation itself, and the terms that matter are settled in settings where a company can still choose how much to disclose. Two pledges have removed the most visible obstacle to those talks. They have not decided what the talks will produce.
