All success stories
ClientOne37
Digital Identity & Verifiable Credentials · Success story
A secure AWS foundation for a digital identity platform
CloudVests moved One37's platform foundation from Azure Kubernetes Service to Amazon EKS, with Terraform-managed infrastructure and key custody in AWS KMS.
ClientOne37Selected AWS services
Core services in the architecture.
A focused view of the AWS services most representative of this engagement. The complete technical scope is described below.
- 01
AWS EKS - 02
AWS Key Management Service - 03
.jpeg)
AWS EBS - 04
AWS Secrets Manager - 05
Elastic Load Balancing - 06
AWS Certificate Manager - 07
Amazon VPC
The challenge
One37's digital identity platform ran its test and staging environments on Azure Kubernetes Service, which did not meet the availability, key custody and SOC 2 evidence its regulated customers expect.
What CloudVests delivered
CloudVests designed the AWS landing zone and provisioned isolated test and staging environments on Amazon EKS across three Availability Zones, all through Terraform.
At One37's request, PostgreSQL, Dragonfly and SigNoz stay self-hosted on EKS, encrypted with AWS KMS and protected by automated EBS snapshots. A KMS key hierarchy secures the platform's identity, messaging and credential-signing keys.
One37's Helm charts were adapted for EKS and its GitLab CI pipeline. An ArchMate assessment against SOC 2 and a Well-Architected review validated both environments before One37's team migrated its data.
The outcome
One37 now runs on Terraform-managed AWS environments, with encryption keys under AWS KMS and SOC 2-aligned controls.
A documented deployment pattern lets the team launch new environments in other AWS Regions as customers require.