Case study
Security Gaps Closed and a Repeatable Upgrade Path for a US Bank
How SquareShift moved a global US commercial bank's Elasticsearch clusters to version 8.x with custom Ansible playbooks, patched known security weaknesses, and mapped a path for its next upgrade.
Book a session →
Client
A large, long-established American commercial bank with more than $1 billion in annual revenue, operating across Asia-Pacific, Europe, the Middle East, and North America.
Industry
Financial Services
Services
Stack
Elasticsearch · Ansible · Terraform · ECK (Elastic Cloud on Kubernetes)
How did SquareShift upgrade the bank's Elasticsearch clusters to version 8.x?
The challenge
The client's on-premises Elasticsearch clusters ran on version 7.17, and Ansible, its automation tool, had stopped supporting the newer version 8.x. Critical banking and transaction systems across four regions depended on these clusters staying up.
What we delivered
SquareShift wrote custom Ansible playbooks that could handle the move to version 8.x, and ran a security review that found and patched known weaknesses. The team also checked Terraform and Elastic's Kubernetes Operator as options for managing the systems in the future.
The outcome
The bank's clusters now run on Elasticsearch 8.x, the known weaknesses are patched, and the bank has a tested, evaluated path for its next upgrade. We plan and run upgrades like this as part of our Elasticsearch migration services.
When a vendor's own automation stops supporting the version you need, the fix isn't to wait for support — it's to write the playbook yourself and hand it over.
Platform & Software Engineering Practice Lead, SquareShift
