Case study
Elastic Cloud Enterprise Upgrade & Storage Optimization
How SquareShift upgraded Elastic Cloud Enterprise and rebalanced storage for a private bank's global traffic-monitoring platform.
The real fix wasn't a version bump — it was giving the bank's own team the muscle memory to run ECE without us next time.
Cloud Modernization Practice Lead, SquareShift
One of Asia's largest private-sector banks, serving more than 70 million customers through online and mobile banking.
It runs high-volume traffic monitoring across global infrastructure on Elastic Cloud Enterprise.
- ECE upgraded to v1.12 across the full production cluster.
- Storage rebalanced onto dedicated warm-tier nodes.
- Internal IT team trained to operate ECE independently.
How SquareShift delivered it.
The challenge
The bank ran Elastic Cloud Enterprise for traffic monitoring but leaned on third-party infrastructure for storage, and performance was starting to slip. Without deep in-house Elastic expertise, the team couldn’t isolate whether the bottleneck was configuration, storage, or the ECE version itself.
With more than 70 million customers routing through online and mobile banking on this infrastructure, an extended performance dip wasn’t a place to experiment.
What we delivered
SquareShift worked alongside the bank’s internal team to run cluster-wide health checks and pin down where the bottlenecks actually lived, then upgraded the platform to ECE v1.12.
Storage moved off generic infrastructure and onto dedicated warm-tier nodes, with node roles restructured to balance performance against storage cost — and the approach was handed over through hands-on knowledge-transfer sessions, not left as a black box for the client to reverse-engineer later.
The payoff
The bank’s traffic-monitoring platform now runs on a current ECE release, with storage purpose-built for its access patterns instead of borrowed third-party infrastructure.
Just as important, the in-house team that once lacked ECE expertise can now run health checks, manage node roles, and maintain the platform on its own.
Where this work sits
