Oracle Exadata on AWS 2026: A UK Buyer's Guide

What actually changed this month

Oracle has announced general availability of Oracle Exadata Database Service on Exascale Infrastructure on Oracle AI Database@AWS, bringing its engineered database hardware into Amazon's data centres a year after the lower-tier Database@AWS service reached general availability in July 2025.

AWS was the last of the major hyperscalers to get this treatment, following Oracle's earlier tie-ups. Alongside the Exadata rollout, AWS and Oracle have signed a new long-term strategic collaboration agreement aimed at helping customers migrate workloads onto the joint service.

The licensing maths UK buyers can't skip

For organisations bringing their own licences (BYOL), Database@AWS uses a ratio of one processor licence per 8 ECPUs, compared with the traditional one processor licence per 2 vCPUs when running Oracle on RDS or EC2 — a metric Nick Walter, CTO and VP of professional consulting services at House of Brick, describes as genuinely more favourable on paper.

But the saving is only half the story. Walter warns that compute and storage costs on Database@AWS run 'much higher than traditional RDS/EC2', and capacity options are far less granular, making right-sizing harder. The Exadata Exascale tier improves granularity and can suit organisations with smaller Oracle fleets, but it doesn't remove the underlying cost gap versus native AWS database services.

Teams evaluating this trade-off should run the numbers properly rather than trust a vendor slide deck — it's worth trying to calculate your cloud vs on-premise TCO before signing anything.

Oracle's FUD and the hyperscaler balancing act

Craig Guarente, founder and CEO of Palisade Compliance, has flagged a pattern of Oracle applying pressure to steer migration decisions — including suggestions that customers could face doubled licence requirements if they run generic Oracle databases on rival clouds rather than through Oracle's own service. He describes this as Oracle creating 'artificial business blockers' to keep spend flowing through its own commercial channels.

Underneath the joint marketing, the hyperscalers and Oracle remain commercial rivals. AWS is simultaneously promoting its Bedrock AI tooling to help customers shift Oracle database applications onto AWS's own PostgreSQL services — a direct play for the same workloads Database@AWS is meant to retain.

As Guarente puts it, the vendors are 'in this weird state of cooperation with Oracle, where now they're all authorised cloud providers,' even as sales teams compete hard behind the scenes.

Is the Exadata hardware premium worth it?

The current Exadata X11M platform, on AMD Turin processors, can deliver up to 2,880 cores and 42TB of memory per rack for database processing, alongside up to 8.5TB/sec of I/O bandwidth and up to 25.2 million 8KB read IOPS per rack — figures that explain why Oracle positions Exadata as suited to demanding, high-transaction workloads rather than general-purpose databases.

Exascale storage pricing per GB is reported to be competitive with AWS's EBS GP3 tier while offering higher throughput, which narrows the gap for storage-heavy applications. Compute remains the sticking point: it's priced above equivalent EC2 or RDS capacity regardless of which Exadata tier is used.

Buyers still running Exadata on-prem should weigh whether that investment is genuinely reaching end of useful economic life before assuming a cloud move is cheaper — organisations specifying an Oracle database server today have more flexibility than those locked into legacy Exadata agreements.

UK-specific considerations before committing

Database@AWS launched from US East and US West before expanding, reportedly reaching 20 global regions by mid-2026, which now brings the practical question of UK latency, data residency and procurement timelines into sharper focus for regulated sectors.

Buyers with existing legacy Exadata contracts — a group Guarente says remains large — need to check how those terms interact with Database@AWS pricing before assuming BYOL savings apply cleanly. Involving expert IT procurement services early avoids nasty contractual surprises later.

For workloads that don't need Exadata-class performance, it's also worth revisiting whether storage solutions for business-critical applications on standard cloud storage tiers meet the requirement at a fraction of the cost.

A practical decision framework

House of Brick's advice is blunt: Database@AWS suits organisations that are licence-constrained and need Oracle in the cloud, but buyers should be alert to sales reps who tout licence savings without mentioning the higher compute and storage bill. Modelling both scenarios — and factoring in support costs through Oracle third-party maintenance options for ageing on-prem estates — gives a fuller cost picture than either vendor's headline figures.