AWS Blue Marlin - Building 1
Hamlet, Richmond County, North Carolina
Parcel boundary
Someone has proposed it. Nothing has been approved and nothing is being built.
Status inferred from cleanview directory (Sep 8, 2026). No filing states it in as many words.
- Status
- Proposed (inferred)
- Owner
- Amazon (AWS)
- Capacity
- 65 MW directory claim
- Location known to
- Parcel boundary
- County
- Richmond County
- State
- North Carolina
- Electric utility
- Not identified
- Grid operator
- not stated
Location and nearby
AWS Blue Marlin - Building 1 is on record as proposed in Richmond County, North Carolina. A directory lists its capacity at 65 MW; no filing we hold states a figure. 2 other campuses are on record within 25 miles. The nearest is 8.2 mi away, measured between approximate points.
Nearest of each kind: Under construction 8.2 mi Proposed 8.2 mi
Nearest campuses on record
- 8.2 mi approximate
Terra Nexus data center campus (316 Old Cheraw Highway)
Proposed · Richmond County, NC
- 8.2 mi
AWS Richmond County (Energy Way)
Under construction · Richmond County, NC
What is on record
Owner
Amazon (AWS) Strong
The chain
-
assessor parcel owner of record
AMAZON DATA SERVICES INC C/O AMAZON.COM INC
NC OneMap statewide parcels (point queries) · Sep 9, 2026
Filed by: AMAZON DATA SERVICES INC C
- Capacity
- 65 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 Blue Marlin - Building 10 · AWS Blue Marlin - Building 11 · AWS Blue Marlin - Building 12 · AWS Blue Marlin - Building 13 · AWS Blue Marlin - Building 14 · AWS Blue Marlin - Building 15 and 16 more
How the status changed
- Under construction Jun 18, 2026 inferred
DCE status 'under_construction'
- 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)
- 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
Primary record
A government filing, a federal permit, an assessor parcel or the operator’s own page.
Location known to
Parcel boundary
Matched to an assessor parcel, so the boundary is the parcel. The point comes from a directory, which does not say how it was derived.
Independent sources
2
assessor parcel, directory. Directories count once between them, because they copy each other.
Spotted something wrong? Tell us and we will fix it.
Where this comes from
22 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 Richmond County
Each time we refresh the public records and a new campus appears in Richmond County, you get one short email naming it, with the document behind it.