![\"Aspect](\"https:\/\/devoteam.info\/wp-content\/uploads\/2025\/04\/aspect.photo_.image_.jpeg\")
<\/a><\/figure>\n\n\t\t\n\t\tAspect has traditionally maintained most of its Microsoft stack applications and databases on-premises. Devoteam is assisting Aspect Capital to migrate several key workloads to AWS.<\/p>\n\n\n\n
The Challenge<\/h2>\n\n\n\n
Aspect Capital previously relied on workload automation solutions to perform routine tasks, such as Extract Transform Load (ETL), data analysis and forecasting, reporting, and signalling to other workloads.<\/p>\n\n\n\n
The large number of tasks performed by these workflows was highly compute-intensive and ran on expensive static machines; often overprovisioned and underutilised between workflow executions. Scaling out when workloads spiked unexpectedly was difficult, given the inelastic nature of the static hosts.<\/p>\n\n\n\n
The environments were all managed by in-house staff, which carried a large amount of unwanted overhead. This was a concern for business continuity and disaster recovery as well.<\/p>\n\n\n\n
The challenge for Devoteam was to migrate a workload designed to make use of a more elastic compute solution, include orchestrated infrastructure deployments, and provide more control and flexibility of costs.<\/p>\n\n\n\n
The Solution<\/h2>\n\n\n\n
As part of the AWS Migration Acceleration Program (MAP), Devoteam worked closely with members of Aspect Capital\u2019s infrastructure and development teams to perform several exploratory proof of concept (PoC) exercises before augmenting both teams on a day-to-day basis to deliver a working end-to-end solution.<\/p>\n\n\n\n
Amazon Managed Workflows for Apache Airflow (MWAA) was wrapped in a reusable and highly configurable bespoke Terraform module. This module not only conforms to Aspect\u2019s own high-security requirements but also to AWS Well-Architected Framework best practices.<\/p>\n\n\n\n
AWS Elastic Container Service (ECS) was adopted to host containerised tasks and sub-tasks from the wider workflows. ECS containers are currently hosted on autoscaling AWS Elastic Compute Cloud (EC2) clusters due to the client\u2019s high floating-point precision requirements having ruled out the immediate use of Fargate (AWS serverless compute for containers).<\/p>\n\n\n\n
Further migration to Fargate containers can now be easily achieved when the Fargate service can provide the precision that Aspect requires. Baseline EC2 capacity can be purchased upfront, using Reserved Instances, to realise a significant cost discount.<\/p>\n\n\n\n
Logging and monitoring of the entire solution is now provided by use of:<\/p>\n\n\n\n
- \n
- AWS CloudWatch Logs (covering MWAA, ECS, EC2, and app logs)<\/li>\n\n\n\n
- AWS CloudWatch Alarms<\/li>\n\n\n\n
- AWS CloudWatch Log Metrics<\/li>\n\n\n\n
- AWS CloudWatch Metrics<\/li>\n\n\n\n
- AWS Simple Notification Service (SNS)<\/li>\n\n\n\n
- OpsGenie integrations<\/li>\n\n\n\n
- Searchable audit logs \u2013 written by the MWAA service<\/li>\n<\/ul>\n\n\n\n
Finally, Devoteam and Aspect team members collaborated on testing of Direct Acyclic Graphs (DAG) within Airflow, to help prepare Aspect Capital for future workload migrations and automated Continuous Integration (CI) pipelines. These pipelines are used for building and deploying DAGs to different MWAA environments and were constructed on top of Aspect\u2019s existing Jenkins CI solution.<\/p>\n\n\n\n
<\/div>\n\n\n\n<\/span><\/div>\n\n\nYour Success Starts Here<\/strong><\/h2>\n<\/div>\n\n\n\n
\n\nPartner with Devoteam to leverage award-winning tech expertise, agile execution, and a culture of continuous learning.<\/p>\n<\/div>\n\n\n\n