Amazon Web Services
Madison County, Mississippi
Building outline
Recorded as in service.
Status inferred from osm footprint (Sep 8, 2026). No filing states it in as many words.
- Status
- Operating (inferred)
- Owner
- Likely Amazon (AWS)
- Capacity
- 69 MW directory claim
- Location known to
- Building outline
- County
- Madison County
- State
- Mississippi
- Electric utility
- Not identified
- Grid operator
- MISO
Location and nearby
Amazon Web Services is on record as operating in Madison County, Mississippi. A directory lists its capacity at 69 MW; no filing we hold states a figure. 14 other campuses are on record within 25 miles, 2 of them within 5 miles. The nearest is 3.6 mi away, measured between approximate points.
Nearest of each kind: Operating 4.0 mi Under construction 9.2 mi Permitted 13.3 mi Proposed 3.6 mi
Nearest campuses on record
- 3.6 mi approximate
Proposed · Madison County, MS
- 4.0 mi approximate
Operating · Madison County, MS
- 5.6 mi approximate
Proposed · Hinds County, MS
- 9.2 mi approximate
Under construction · Hinds County, MS
- 9.8 mi approximate
Proposed · Hinds County, MS
- 11.3 mi approximate
Proposed · Hinds County, MS
What is on record
Owner
Likely Amazon (AWS)
One circumstantial signal, not a document chain.
What the signal was
-
OSM operator tag
Amazon Web Services
Overpass data_center query, tile conus-c2 bbox 24.0,-95.0,50.0,-85.0 · May 8, 2026
Filed by: Amazon Web Services
- Capacity
- 69 MW as reported by cleanview, not from a filing
- Diesel generators
- No air permit found in the records we collect
- Water
- Not collected. State water withdrawal permits are not in this build.
- Electric utility
- More than one utility serves this county, and no filing we hold names which one
- Also recorded as
- AWS Ridgeland Building 1 · AWS Ridgeland Building 10 · AWS Ridgeland Building 11 · AWS Ridgeland Building 12 · AWS Ridgeland Building 13 · AWS Ridgeland Building 14 and 10 more
Buildings and phases
4 distinct buildings, parcels or permits make up this campus.
| Name or address | Status | Permit | Area | Date |
|---|---|---|---|---|
| Amazon Web Services | Operating | not stated | not stated | May 8, 2026 |
| Amazon Web Services | Operating | not stated | not stated | May 8, 2026 |
| Amazon Web Services | Operating | not stated | not stated | May 8, 2026 |
| Amazon Web Services | Operating | not stated | not stated | May 8, 2026 |
How the status changed
- Operating May 8, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c2 bbox 24.0,-95.0,50.0,-85.0
- Operating May 8, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c2 bbox 24.0,-95.0,50.0,-85.0
- Operating May 8, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c2 bbox 24.0,-95.0,50.0,-85.0
- Operating May 8, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c2 bbox 24.0,-95.0,50.0,-85.0
- Operating Jun 18, 2026 inferred
DCE status 'mapped' (located only, single source)
- Operating Sep 8, 2026 inferred
Cleanview status 'Operating'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Operating Sep 8, 2026 inferred
Cleanview status 'Operating'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Operating Sep 8, 2026 inferred
Cleanview status 'Operating'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Operating Sep 8, 2026 inferred
Cleanview status 'Operating'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Proposed Sep 8, 2026 inferred
Cleanview status 'Planned'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Proposed Sep 8, 2026 inferred
Cleanview status 'Planned'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Proposed Sep 8, 2026 inferred
Cleanview status 'Planned'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Proposed Sep 8, 2026 inferred
Cleanview status 'Planned'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Proposed Sep 8, 2026 inferred
Cleanview status 'Planned'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Proposed Sep 8, 2026 inferred
Cleanview status 'Planned'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Proposed Sep 8, 2026 inferred
Cleanview status 'Planned'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Proposed Sep 8, 2026 inferred
Cleanview status 'Planned'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Proposed Sep 8, 2026 inferred
Cleanview status 'Planned'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Proposed Sep 8, 2026 inferred
Cleanview status 'Planned'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
About this data
Evidence
Map footprint and directories
An OpenStreetMap footprint plus one or more directories. No filing behind it.
Location known to
Building outline
A mapped building outline.
Independent sources
2
directory, osm footprint. Directories count once between them, because they copy each other.
Spotted something wrong? Tell us and we will fix it.
Where this comes from
19 source records back this page. Each row is a document we retrieved and kept, so a claim can be checked against the original.
Cleanview (cleanview.co) © DataCentersExposed contributors, datacentersexposed.com, ODbL 1.0. Contains data © OpenStreetMap contributors.
Free email alerts
Know first when a data center is recorded in Madison County
Each time we refresh the public records and a new campus appears in Madison County, you get one short email naming it, with the document behind it.