x8aedz.xlarge is AWS's memory-optimized EC2 size at 4 vCPU and 128 GiB. The nearest Rackspace Spot server is mh.vs1.2xlarge at 16 vCPU and 128 GiB, which is 12 more vCPU than the AWS x8aedz.xlarge.
Regions are Rackspace Spot locations.
| Region | AWS on-demand | AWS Spot | 1-yr Reserved | 3-yr Reserved | Rackspace on-demand | Rackspace Spot | On-demand price savings | Spot price savings |
|---|---|---|---|---|---|---|---|---|
| US East, N. Virginia | not sold here | n/a | n/a | n/a | $0.431 | $0.021 | n/a | n/a |
| US Central, Chicago | no AWS region | n/a | n/a | n/a | $0.464 | $0.021 | n/a | n/a |
| US Central, Dallas | no AWS region | n/a | n/a | n/a | $0.463 | $0.131 | n/a | n/a |
| Hong Kong | not sold here | n/a | n/a | n/a | $0.494 | $0.021 | n/a | n/a |
| Sydney, Australia | not sold here | n/a | n/a | n/a | $0.491 | $0.191 | n/a | n/a |
| London, UK | not sold here | n/a | n/a | n/a | $0.420 | $0.029 | n/a | n/a |
| US West, San Jose | not sold here | n/a | n/a | n/a | $0.440 | $0.002 | n/a | n/a |
| US Central, Dallas 2 | no AWS region | n/a | n/a | n/a | $0.440 | $0.242 | n/a | n/a |
Prices updated 18 Nov 2026.
AWS publishes no on-demand price for x8aedz.xlarge in any of the regions this page covers, because it is not sold there. The specifications and the Rackspace Spot prices below still apply. Rackspace Spot also sells in Chicago and Dallas, where AWS operates no region at all, so those rows have no AWS price to compare against.
mh.vs1.2xlarge, at 16 vCPU and 128 GiB, with 12 more vCPU and the same memory against x8aedz.xlarge. Prices per region are in the table above. Rackspace Spot classes are region-suffixed, so the exact name differs per row.
No. x8aedz.xlarge ships 1 × 316 GB of local NVMe SSD, rated 89,444 read IOPS. Rackspace Spot servers are network-backed, so a workload that leans on local disk throughput needs block storage or a re-architecture. Everything else about the match still holds.
Rackspace Spot mh.vs1.2xlarge is the closest shape; the table above shows current prices by region. Workloads have to be containerized to run on it.