Cloud strategy for the bank: public, private, hybrid
Regulator requires data residency, ABS requires low latency, economics requires elasticity. Per-workload frame.
Discuss Your ChallengeWhen the fork appears
Bank decides infrastructure strategy. Public cloud (AWS, Azure, GCP) elastic + managed services. Private (on-prem or managed) — control + residency. In UZ — local clouds (UCell Cloud, Beeline Cloud) with regulatory positioning but limited services.
cbu.uz cloud guidelines tightening — bank must engage early.
Per-workload criteria
Data residency. PII in country — disqualifier for public cloud without local region.
Latency. ABS, card processing, payments — low latency. Public cloud distant — disqualifier.
Workload variability. Marketing campaigns spiky — public elastic. ABS steady — private cheaper.
Managed services. ML, analytics — public faster. Custom — less benefit.
Vendor lock-in. Public — managed services lock-in. Private — hardware/licence.
Regulatory openness. Regulator position changes — must be tracked.
Per-workload split typical
Customer-facing apps & decisioning — local cloud / private (latency).
CRM, marketing, analytics — public (if data residency allows).
ABS, biller, ledger — private (residency, low risk tolerance).
ML training — public for elasticity, serving — local.
DR / backup — multi-region public.
Where decisions usually go wrong
“All public” without regulatory check. Regulator complaint.
“All private” — misses elasticity benefits.
Lift-and-shift to public — TCO higher than on-prem.
Vendor lock-in without exit story.
What to discuss at the committee
Data residency requirements per workload — regulator clarification.
Per-workload 5-year TCO.
Skill set audit and hire/retrain plan.
Vendor lock-in mitigation.
cbu.uz cloud guidelines update.
Related
Ready to discuss your challenge?
Tell me what's not working or what needs to be built. First conversation — no obligations.
Usually respond within a few hours