Science & Tech · AI · 7 hrs ago
ANZ moves 1.7PB data platform to AWS in six months with AI
ANZ moved its big data platform to AWS in six months, a year faster than the bank expected.
The platform moved from Cloudera Hadoop, which ANZ had run on its own infrastructure, to Amazon EMR, an AWS service for processing data.
The migration covered 1.7 petabytes of data, along with millions of files, tables and automated workflows.
ANZ says coding and troubleshooting AI agents cut the migration effort by 35% and halved defects and rework compared with traditional approaches.
The platform supports the bank’s payments, customer remediation, and business and private banking operations.
ANZ tokenised almost 80 terabytes of sensitive data to protect customer information, and says the process now runs about seven times faster at a much lower operating cost.
The bank says it is also building a reusable AI platform for its own systems and cloud services.
ANZ moved its enterprise big data platform from on-premises Cloudera Hadoop to Amazon EMR on AWS in six months, a year faster than anticipated.
The migration covered 1.7 petabytes of data across 300 million files, 142,000 tables, 4,500 automated workflows and 4,000 views.
ANZ said agentic AI reduced migration effort by an estimated 35 percent and cut defects and rework by about half compared with traditional approaches.
The platform supports the bank’s payments, customer remediation, and business and private banking operations.
ANZ has tokenised almost 80 terabytes of sensitive customer data, with the process running about seven times faster and costing less.
- Who
- ANZ Banking Group, working with AWS Professional Services, AWS partners and its own engineers.
- What
- ANZ migrated its enterprise big data platform from on-premises Cloudera Hadoop to Amazon EMR on AWS, using AI-assisted engineering.
- When
- The migration took six months. The anticipated schedule was 18 months.
- Where
- From an on-premises environment to Amazon Web Services.
- Why
- ANZ said the modernisation was needed to provide good-quality data and a scalable lakehouse architecture.
This story does not have two clearly opposing sides.
This story does not have a timeline yet.
- Migration duration
- Six months
- Original anticipated schedule
- 18 months
- Data volume
- 1.7 petabytes
- Files
- 300 million
- Automated workflows
- 4,500
- Tokenised data
- Almost 80 terabytes
What people are saying
hothouse environment
accelerate complex delivery while maintaining a disciplined focus on security, resilience and quality