While the migration has gone well, financial leaders were concerned about the visibility of spending and the risk of ‘bill shock’. GEL asked TSL to help it improve its visibility into its use of AWS services and help reduce costs by implementing its FinOps methodology. “We like and trust TSL,” says Katherine Stubbings, head of the office of chief information officer at GEL. “They understand the uniqueness of our set-up—we’re not a 24/7 ecommerce business, but we’re not a 9–5 corporate either. They’re the right size for us and can flex with us when needed, and have all the skills of a big player but are much more agile and available.”
GEL spending is spread across departments with fast-moving and varied technology requirements and systems. FinOps required a cultural change for engineers focused on solutions to improve services for diagnostics and researchers. The migration of hundreds of servers and hundreds of terabytes of data meant not all applications had been re-architected as planned.
TSL helped GEL visualize, understand, and manage its AWS costs and usage over time by using various tools such as a business intelligence (BI) dashboard based on Tableau Server on AWS linked to AWS Cost Explorer. This helped GEL find under-utilized or over-provisioned capabilities. Then, using TSL’s hierarchical FinOps methodology, it implemented serverless processes to automate SLA-based system runtimes. This included scheduled auto stop/start of test environments that were running 24/7. Switching off non-production Amazon Elastic Compute Cloud (Amazon EC2) and Amazon Relational Database Service (Amazon RDS) instances outside of working hours contributed 67 percent of total non-production savings of £1 million per year.
A key part of the FinOps methodology implemented by TSL was to provide FinOps ‘Golden Paths’ for the GEL engineers. These provided full documentation, together with example scenarios and code, so that moving forward, all platform engineering incorporated FinOps from the inception design. The BI dashboard and Golden Paths, together with increasing acceptance of FinOps has allowed GEL to hand responsibility back to individual departments, which in turn have been able to fund new projects and innovations by finding savings in their existing AWS usage. Now GEL teams are better able to match instances to workloads using Amazon EC2 for secure, resizable compute capacity in the cloud, and use Amazon RDS to remove inefficient and time-consuming database administrative tasks. GEL and TSL are still working on re-architecting applications and services to support a longer-term shift to microservices and alternative application architectures including more use of serverless technologies like AWS Lambda and AWS Fargate.
The teams are also seeking to increase efficiency and sustainability by more use of workloads running on AWS Graviton Processors. “The huge growth in our data means we have to be highly efficient just to keep functioning,” says Stubbings. “If we were still operating as we were a year ago, we could not afford to keep going, it’s a big challenge.”
Genomics England is very aware of its legal and ethical responsibilities to keep people’s most personal and sensitive information secure. The collection of processes that make up the pipeline from taking samples, storing, processing, and providing diagnostic advice are considered a medical device requiring ISO 13485 compliance and associated audits. “Genes don’t change—it is our most personal data and there’s an emotional consideration, too,” says Stubbings, “We take that responsibility seriously and appreciate sharing that responsibility with AWS.”