1. Amazon Web Services drops data center NDAs: what was announced?
Amazon Web Services (AWS) said it will stop asking government agencies to sign non-disclosure agreements on its data center projects. AWS chief executive Matt Garman announced the change on October 2, 2026, placing the company alongside Microsoft, which committed in March 2026 to end such agreements with local governments. AWS also pledged more than $1 billion over five years to a community program called Built Together.
The announcement matters because data centers, the large facilities that house the computing hardware behind cloud services and artificial intelligence, have become one of the most contested forms of new development in the United States. Confidentiality clauses attached to their approval were a recurring complaint among residents, who often learned the scale of a proposed project only after officials had already moved far down the negotiating path.
Garman's statement covers government agencies that work with AWS on data center projects. Under the new policy those agencies will no longer be bound to keep their discussions with the company confidential. The change is narrow in one sense, because it addresses a single contractual tool, but it speaks directly to the question that has driven much of the local opposition: who gets to know what, and when.
2. What is an NDA in a data center negotiation?
A non-disclosure agreement is a contract that bars the people who sign it from sharing specified information. In ordinary corporate dealings, NDAs protect trade secrets, pricing and product plans. In data center development, they have taken on a different role, because the other party is frequently a town council, a county board or a state economic development office rather than another business.
When a technology company scouts a location, it typically discusses land, power supply, water access, tax incentives and zoning with public officials. If those officials have signed an NDA, they can hold those conversations but cannot describe them to the public. Residents may therefore hear nothing until a deal is well advanced, at which point a hearing or vote can feel like a formality rather than a decision still open to influence.
Companies have generally defended confidentiality at this stage as a normal part of site selection, arguing that early disclosure can expose a project to competitors or drive up land prices. Critics respond that the same secrecy, applied to public bodies spending public resources and granting public approvals, leaves communities unable to weigh costs and benefits in time. AWS's decision effectively concedes that the second argument has gained more weight than the first.
3. What is the Built Together program?
Built Together is the other half of the announcement. AWS has committed more than $1 billion over five years to projects in the communities that host its data centers. The company said the money will concentrate on education, job creation and energy accessibility, three areas that map closely onto the benefits and burdens local residents most often raise when a facility is proposed nearby.
Education and job creation address the concern that data centers employ relatively few people once construction ends, despite their size and the investment they represent. Energy accessibility addresses the worry that large new electricity demand can raise costs or strain supply for neighbors. A funding program aimed at those themes signals that AWS expects the debate to center on tangible local returns rather than on technical details of the buildings themselves.
The scale of the pledge deserves context. A commitment of more than $1 billion is large in absolute terms, but it is spread across five years and across every community where AWS operates. How much any single town receives will depend on how the company distributes the funds, and the announcement as described does not specify an allocation formula. Local officials and residents will likely judge the program by what reaches their own area rather than by the headline total.
4. Why did secrecy become a liability for Big Tech?
The timing of the announcement reflects a wider shift in public attitudes. More than 100 data center moratoriums are under consideration across the United States, according to the context AWS and others have cited when explaining their policy changes. A moratorium pauses approvals for new facilities, usually while a local government studies their effects, and the volume of such proposals shows how quickly sentiment has moved in some places.
Both AWS and Microsoft have described their decisions as responses to public scrutiny and local opposition. Confidentiality clauses have become a kind of shorthand for residents' distrust: even when an agreement protects nothing more than routine commercial details, its existence suggests to many people that something is being kept from them. Removing the clauses is therefore as much a signal about intent as a change in legal mechanics.
There is also a practical business logic. Projects that face organized resistance can be delayed, redesigned or abandoned, and each delay is costly when companies are racing to add computing capacity for artificial intelligence. If openness at the start reduces the odds of a later fight, a company can reasonably decide that the loss of early confidentiality is worth accepting.
5. How did Congress and Microsoft shape the decision?
Political pressure arrived shortly before the announcement. On September 30, 2026, Representative Jamie Raskin opened a congressional inquiry into NDA practices at large technology companies, naming Amazon and Google. AWS announced its policy change two days later, a sequence that suggests the inquiry accelerated, or at least coincided with, the company's decision.
Microsoft had moved first. In March 2026 it committed to ending NDAs with local governments, which meant that by early October the pledge was no longer an outlier among the largest cloud providers. Once one major company drops a practice and a second follows, the remaining firms face a harder time explaining why they still need it.
Google was named alongside Amazon in Raskin's inquiry, and with Microsoft and AWS both having abandoned government NDAs, the pressure on Google to explain its own approach is unlikely to ease. Whether it follows with a similar pledge, or defends its current practices, is one of the open questions the episode leaves behind.
6. What does the change mean for local governments and residents?
For officials negotiating with AWS, the most direct effect is freedom to talk. Council members, county staff and agency leaders can now discuss the terms of a proposed project with constituents without worrying that they are breaching a contract. That is a practical improvement for local governments, which are often expected to make complex decisions about power, land and incentives while also keeping the public informed.
For residents, it opens the possibility of earlier and fuller information. People who might object to a project, or who might support it for the jobs and tax revenue it brings, can engage while the terms are still being shaped. Public input offered early tends to be more useful to both sides than reaction offered after the outline of a deal is settled.
The limits are worth stating plainly. The policy applies to government agencies and to AWS's own projects. It does not by itself guarantee that every detail of a negotiation will be published, since companies and officials retain other ways to keep certain business information private. The announcement as described also does not explain what happens to agreements signed before the change, so the effect on projects already under way remains unclear.
7. Why do data centers depend so heavily on local approval?
A modern data center is a large industrial building. It draws substantial electricity, needs reliable cooling, occupies considerable land and connects to power and fiber networks that other users also rely on. Each of those requirements usually runs through a local or regional decision-maker: a zoning board approves land use, a utility agrees to supply power, and a government office may offer tax treatment that shapes the project's economics.
Because so many public bodies are involved, the information flow around a project is unusually important. Residents who live near the proposed site want to know about noise, traffic, water use and the load on the electrical grid. Taxpayers want to know what incentives are being offered. Officials want to be able to answer those questions without legal hesitation, and an NDA made that difficult by design.
The rise of artificial intelligence has raised the stakes. Training and running advanced models requires dense clusters of specialized chips, and the companies building them are expanding capacity at a pace that tests local infrastructure. As projects grow larger and more numerous, the number of communities confronting these questions grows with them, which helps explain why a procedural issue like confidentiality has turned into a national talking point.
Seen in that light, the decision by AWS is less a stand-alone gesture than a recognition of how development now works. Approval depends on public consent, public consent depends on public information, and a company that wants to keep building has an interest in making that information easier to obtain.
8. What comes next for AWS and the data center debate?
The next test is implementation. Observers will watch whether AWS applies the new policy consistently in upcoming negotiations, whether officials actually begin disclosing more, and how the company distributes Built Together funds across host communities over the five-year period.
Pressure on other companies is the second thing to follow. Google remains named in the congressional inquiry, and further responses to Representative Raskin's questions could show whether the industry is converging on a common standard of openness or splitting between firms that keep confidentiality and firms that drop it.
The broader debate over data center growth will continue regardless. The number of moratoriums under consideration shows that transparency alone may not settle local concerns about electricity demand, land use and the permanence of the jobs created. Ending NDAs removes one source of friction, but the larger question of how communities share in the costs and benefits of the artificial intelligence buildout remains open.