IoTWorm

Reported from primary sources

EC2 U7i High Memory Instances Expand to São Paulo and Ireland

Amazon's largest EC2 instances now reach two more regions, giving SAP HANA and Oracle users in South America and Europe local access to up to 24 TiB of DDR5 memory.

Which AWS regions can now run EC2 High Memory U7i instances?

As of July 23, 2026, the u7in-16tb.224xlarge is available in the AWS South America (São Paulo) region, and the u7in-24tb.224xlarge is available in AWS Europe (Ireland). Both belong to Amazon's 7th-generation EC2 lineup and are designed for large in-memory database workloads.

What hardware powers these instances?

Both instance types run on custom fourth-generation Intel Xeon Scalable processors, based on the Sapphire Rapids architecture. They each provide 896 vCPUs, regardless of whether the memory configuration is 16 TiB or 24 TiB of DDR5.

The networking and storage specs are identical across both variants. Each delivers up to 200 Gbps of network bandwidth, up to 100 Gbps of Amazon EBS bandwidth, and support for ENA Express.

Instance specifications

Instance type Memory vCPUs Network bandwidth EBS bandwidth New region
u7in-16tb.224xlarge 16 TiB DDR5 896 200 Gbps 100 Gbps South America (São Paulo)
u7in-24tb.224xlarge 24 TiB DDR5 896 200 Gbps 100 Gbps Europe (Ireland)

Who are these instances built for?

AWS explicitly targets customers running mission-critical in-memory databases, naming SAP HANA, Oracle, and SQL Server as primary use cases. The large DDR5 memory pools are intended to support transaction processing throughput as data volumes grow.

For organizations already running those workloads in AWS, the regional expansion reduces the need to route traffic across long distances to reach the instances. Customers in Brazil and Ireland can now keep data residency local while still accessing the high-memory configurations.

Why does the regional split matter?

The two new regions received different instance sizes: São Paulo gets the 16 TiB variant, while Ireland gets the 24 TiB variant. AWS did not explain the reasoning behind this asymmetry in the announcement.

For enterprises subject to data sovereignty requirements in either geography, the availability of these instances locally removes a significant architectural constraint that previously forced a choice between compliance and raw memory capacity.