Amazon’s Built Together: $1 Billion for Data Center Towns and No More Government NDAs

On October 2, 2026, Amazon published a post by Matt Garman, CEO of Amazon Web Services, with two parts. The first is a written list of tenets it calls the Amazon Data Center Commitment, also posted as a standalone page. Among them: Amazon says it works with utilities, regulators and grid operators so that the energy prices it pays are sufficient to cover both the energy and the infrastructure improvements its data centers may require; it says “we no longer use nondisclosure agreements with the government agencies we work with on our projects”; it says it will use backup generators at new sites that meet the EPA’s Tier 4 emissions standards or the equivalent elsewhere; it says it designs operations to at least meet local sound requirements at the site perimeter; and it says it will publish its energy use, energy efficiency, water use, water efficiency and percentage of carbon-free energy every year. It also restates a goal of being water positive across its data centers by 2030 and says it was 75 percent of the way there as of 2025.

The second part is Built Together, a community investment program starting in the United States. Amazon says it will add more than $1 billion over the next five years to what it already does, after contributing more than $1 billion over the past three years to U.S. communities where it has a meaningful data center presence. The money is organized in three pillars. Education and workforce: free community college for residents of data center communities, which Amazon estimates will reach more than 300,000 students over five years, and a network of modular training centers. The post says three centers operate today, six are under development and 16 more are planned, which computes to the 25 the program page cites, with a plan to train up to 100,000 people a year by the end of 2028. Energy and water: grants for efficiency upgrades targeting more than 300 schools and community buildings and more than 30,000 homes. Local priorities: what Amazon describes as millions of dollars per year in each community, directed through local nonprofits and community foundations.

Garman’s post is an argument as much as an announcement. It says more than 100 data center moratoriums are being considered across the country, and it spends most of its length disputing claims about water, electricity rates and generator emissions. Those are Amazon’s figures and Amazon’s framing, not PSV findings, and PSV has not verified them. What matters for a developer or landowner is narrower and does not depend on who is right in that argument: one of the country’s largest data center builders has now written down the terms it says it follows, on its own website, where any county attorney, planning commissioner or neighborhood group can read them.

In PSV’s read, that changes the baseline for everyone else in the room. A commitment not to use nondisclosure agreements with government agencies speaks directly to one of the most common complaints in data center site selection, where projects have been negotiated under code names before residents learned who the user was. A Tier 4 generator commitment, a cost-coverage position on electricity and annual public reporting are all things a planning board can now ask any applicant to match and write into conditions of approval. The pledge binds only Amazon, and only to the extent Amazon holds itself to it. But a developer building for a different tenant, or a landowner selling a site, should expect to be asked why their project offers less. The $1 billion also computes to an average of about $200 million a year across all eligible communities, and Amazon has not said how many communities that is.

The artifact is a commitments matrix for a specific project. Inputs: Amazon’s published tenets and the Built Together program page as the comparison set; the project’s own application, development agreement and any incentive agreement; the air permit application and generator specifications; the utility’s large-load tariff or service agreement; the local noise ordinance and the project’s sound study; any confidentiality agreement the project has signed with a public body; and the minutes of prior hearings. Output: one row per tenet, showing what the project has actually committed to, the document and section where that commitment lives, whether it is enforceable as a condition of approval or only a statement, and the gap against the published Amazon standard.

The reviewer is the head of development with land use counsel, and the approval gate is that nothing goes into a hearing presentation, a community flyer or a letter to the county unless it traces to a signed document or a condition the applicant is prepared to accept in writing. An assistant does the reading well: pulling commitments out of long applications and agreements, lining them up against the tenets, and flagging where a public statement has no document behind it. It should not decide what the project offers a community or what the team says under oath. PSV promises no entitlement outcome from any of this.