The Bigger Picture: From Migration to Modernisation
Bringing workloads into AWS – even via Amazon EVS – isn’t just a cost move. It sets the stage for broader cloud transformation:
- Data can now be accessed by AWS AI/ML and analytics services
- Workloads are no longer tied to fixed on-prem infrastructure
- Modernization projects, specifically GenAI innovation projects, can start small, then scale
Once your workloads reside in AWS, you're no longer constrained by the limitations of physical infrastructure. You gain flexibility in how applications evolve, how data is integrated across services, and how your teams adopt new tools. This also creates a smoother path for future transformation: containerization, serverless compute, continuous optimization, and intelligent automation all become easier to explore. Amazon EVS becomes a bridge – not just to AWS, but to a more agile, scalable digital core. This model supports long-term agility while minimizing short-term disruption.
FinOps optimization plays a critical role in cloud strategy. While Amazon EVS offers a path for legacy workloads that must remain on VMware, it is not a low-cost option – it still requires VMware licensing and operational overhead. Organizations can achieve greater cost savings by migrating the majority of their workloads to AWS native services, thereby reducing their VMware footprint and exposure to license cost increases. This targeted approach helps lower VMware license costs and improves the ROI of running in AWS compared to maintaining on-premises infrastructure. Amazon EVS should be promoted as a strategic solution for the workloads that truly require VMware VCF, not as a default lift-and-shift path. For broader migrations, migrating to AWS native services remains the more cost-effective and scalable option.