Skip to content

Architecting Global Scale for a Health & Wellbeing Platform on AWS

Discover how a health & wellbeing platform leveraged a well-architected AWS foundation and Infrastructure as Code to support global expansion, regulatory alignment, and scalable multi-region operations.

cloud-migration-terraform

Client Overview

Humanoo (Acquired by TELUS Health) operating in the healthcare industry, has developed an innovative platform that caters to employee retention and corporate wellness. The platform is designed to provide comprehensive wellness solutions to insurance companies and employers.

By implementing these wellness programs, companies can improve employee satisfaction, reduce absenteeism, and enhance productivity. By leveraging cutting-edge technology and customised wellness programs, the start-up helps companies create a healthier and more supportive work environment that benefits both employees and employers.

The platform operates on AWS and relies on managed cloud services to support scalable, production-grade workloads.

humanoo-logo-colour

Challenge

Following acquisition and accelerated international growth, the platform expanded its AWS footprint across regions while continuing to operate under strict EU-GDPR requirements.

Because the architecture was deliberately designed around segregation of PII and PHI processing domains, scaling internationally required careful preservation of this model within Infrastructure as Code workflows and established compliance controls.

 

Segregation-by-Design at Increased Scale

The intentional separation of PII and PHI workloads introduced architectural considerations that needed to remain consistently enforced as the AWS environment expanded.

Compliance Framework Alignment

Ongoing adherence to EU-GDPR requirements, ISO27001:2022 controls, and AWS CIS Level 3 configuration baselines required structured Infrastructure as Code coverage across services.

Infrastructure Consistency Across Regions

As the AWS footprint grew, maintaining consistent automation patterns and configuration standards became important to preserve governance integrity.

Sustained IaC Coverage

Continuous expansion increased the importance of ensuring that all core services and controls remained codified and version-controlled within Terraform and Terragrunt modules.

Solution

To support accelerated global growth, the platform’s existing Infrastructure as Code and architectural standards were further expanded and refined, strengthening automation coverage and enabling consistent multi-region operations.

  • Infrastructure as Code with Terraform and Terragrunt: The AWS environment was progressively structured through Terraform and Terragrunt modules, extending version-controlled infrastructure management across accounts, regions, and environments. Modular configurations enhanced consistency and maintainability while preserving established governance standards.
  • Multi-Region and Multi-Tenant Architecture Enablement: Existing Infrastructure as Code patterns enabled controlled replication of compliant environments, supporting multi-region expansion and tenant isolation through reusable and standardised deployment workflows.
  • Operational Improvements and Resource Optimisation: Database and caching services were transitioned to Graviton-based instances where appropriate, and scheduled scaling strategies were refined to align resource utilisation with platform demand.
  • Security and Connectivity Alignment: Encryption standards, private connectivity through VPC endpoints, certificate lifecycle management via ACM, and internal service discovery were consistently embedded within Infrastructure as Code definitions to maintain alignment with regulatory and architectural baselines.

This structured evolution reinforced the platform’s automation framework, ensuring scalable growth while maintaining governance integrity and operational consistency.

Results

The continuous investment in Infrastructure as Code and compliance-aligned architecture became a fundamental enabler of the platform’s global expansion.

Infrastructure as Code at Scale

AWS environments are managed through version-controlled Infrastructure as Code, providing structured governance and long-term operational consistency across regions.

Consistent Multi-Region Deployments

Standardised infrastructure modules ensure that environments remain aligned across tenants, services, and AWS regions, enabling predictable and repeatable global rollout.

Governance and Operational Visibility

Centralised automation and configuration management maintain traceability, policy alignment, and operational transparency as the platform evolves.

Scalable Architectural Foundation

Encryption standards, private networking, and certificate lifecycle management remain embedded within the infrastructure model, supporting continued regional and workload expansion without structural rework.

Technology Stack

To support global expansion and sustained Infrastructure as Code practices, the platform leverages a comprehensive set of AWS-native services and tooling designed to maintain architectural consistency, regulatory alignment, and operational transparency across regions.
  • Cloud Platform: Amazon VPC, IAM, ECS Fargate, RDS (MySQL), ElastiCache (Redis), SQS, SNS, Application Load Balancer, Route 53, CloudWatch, S3, KMS, ACM, Transit Gateway, AWS Cloud Map, ECR, Lambda, SSM Parameter Store, Secrets Manager, CloudFront, VPC Endpoints
  • Infrastructure as Code: Terraform, Terragrunt
  • Monitoring & Observability: CloudWatch, New Relic, VPC Flow Logs, CloudTrail

By embedding architectural standards, compliance controls, and automation patterns directly into Infrastructure as Code workflows, the platform operates with a consistent and scalable AWS foundation capable of supporting continued regional growth.

Ready to build a globally scalable AWS foundation designed for long-term growth? Book a consultation with our experts.