AWS drops Trn3 and P6 into a new London zone, and won't say where it is

Amazon Web Services added an availability zone to eu-west-2, its London region, this week, and says the zone carries AI and machine learning capacity including Amazon EC2 Trn3 and P6 accelerated instances alongside general-purpose compute ^[1][2]. For teams that have spent the past two years choosing between keeping training data inside the UK and actually getting hold of accelerators, that is a placement decision they can make now rather than a roadmap item.

The mechanics matter more than the announcement. An availability zone is a data center or a cluster of them, placed in a geographically redundant location inside a cloud region, close enough to the other zones to be useful and far enough to survive a localized incident, according to the reporting ^[3]. That means the new capacity sits inside the same regional boundary that residency-constrained workloads are already scoped to, which is the whole point: no new contract surface, no new region to onboard, no cross-border replication argument with a compliance team.

What AWS has not said is where the thing is. Details of the zone's physical footprint were not provided ^[4]. That is normal for AWS and mostly harmless, though it does sit awkwardly beside the fact that the region marketed as "London" has most of its data centers nearer Bristol ^[5]. Anyone writing latency assumptions or a jurisdictional memo off the region name is working from a label, not a location.

The build pipeline behind this is visible. AWS is developing data centers in Buckinghamshire, north of London ^[6], bought a site in Oxfordshire in December 2025 ^[7], and has previously been linked to projects in Houghton Regis in Bedfordshire, Hayes in Middlesex, Swindon in Wiltshire, and Bracknell in Berkshire ^[8]. None of that is confirmed as feeding this particular zone, but it is the supply curve that determines whether accelerated capacity in eu-west-2 stays scarce.

The unglamorous caveat: the announcement as reported carries no quota, pricing, or volume detail for Trn3 and P6 in the new zone ^[9]. Availability in a zone and availability to your account are different problems, and capacity for large training instances has generally been the second kind.

The same week, AWS made a Las Vegas Local Zone generally available as a child of the US West Oregon region ^[10][11]. Local Zones are edge locations offering a selected subset of services close to population centers, often where Amazon has no existing footprint ^[12], and they can sit in third-party data centers as well as Amazon-owned facilities outside a geographic region ^[13]. Las Vegas supports EC2 C7i, M7i, R7i and C8gn, EBS gp3, gp2, io1, sc1 and st1, ECS, EKS, Application Load Balancer, and Direct Connect ^[14]. That list contains no accelerator family ^[15]. Local Zones started in the US in 2019, there are now more than 30 in international markets, and this year's additions include Istanbul, Hanoi, and Athens ^[16][17].

Two things to watch. Whether Trn3 and P6 in eu-west-2 turn out to be orderable at useful scale, or a headline attached to a waitlist. And whether the Buckinghamshire and Oxfordshire builds surface as further zones in the same region, which is what would actually move UK accelerated capacity from tight to routine.