AWS Migration and CI/CD Automation for a B2B Software Company
27
cloud applications
2
months to complete
200
client's saved hours
Key Insights
Location
Western Europe
Project duration
2 months
Industry
B2B Software
Technologies used
AWS, Terraform, Docker, Amazon ECS, CI/CD Automation, SOC2 Compliance Architecture, PostgreSQL
Services
Introduction
A growing B2B software company partnered with Perfsys to move its infrastructure from Microsoft Azure to Amazon Web Services (AWS) . The goal was to build a secure, compliant, and developer-friendly platform that could handle increasing demand and simplify software delivery.
Perfsys led the migration process, set up full CI/CD automation, and deployed production-ready infrastructure in line with SOC2 requirements and cloud engineering best practices.
Background
The company initially built its entire platform on Microsoft Azure using services like AKS (Kubernetes), Blob Storage, Cosmos DB (Gremlin), Azure Tables, and Azure Pipelines. This setup worked during early development but began showing limitations ahead of a public launch.
Issues like unreliable environment isolation, difficulty managing secrets, and fragmented automation slowed down development. As the team prepared for SOC2 certification and larger user loads, it became clear that they needed a new cloud setup.
Perfsys was brought in to support the move to AWS and design a scalable system with strong automation, better structure, and long-term maintainability.
Challenges
The existing Azure setup created several roadblocks:
- Inflexible environments made it hard to spin up temporary test or staging systems.
- CI/CD workflows lacked consistency, slowing down releases.
- Role management and access control were hard to manage at scale.
- Monitoring and alerting had to be set up manually, making compliance harder.
- Observability and cost control were limited for Kubernetes workloads.
The company needed a complete migration plan that would improve structure, support automation, and keep data secure across cloud services, APIs, and databases.
Solution Overview
Perfsys delivered the solution in five structured phases, each focused on delivering clear results tied to business needs.
Milestone 1: Discovery and Planning
Work began with a deep assessment of the company's Azure environment. Perfsys:
- Evaluated cloud service dependencies and mapped architecture components.
- Gathered compliance requirements for SOC2.
- Reviewed the CI/CD process in Azure DevOps.
- Audited Kubernetes setup for scaling and storage needs.
Key deliverables included a network design, IAM and access role plan, and a roadmap for replacing services with AWS alternatives.
Milestone 2: AWS Organization and Identity Setup
Perfsys created a solid foundation for secure and manageable cloud operations:
- Deployed an AWS Organization with separate accounts for production, staging, and development.
- Set up AWS IAM Identity Center (SSO) linked to Google Workspace.
- Created access policies tailored for developers, administrators, and auditors.
- Centralized logging and audit trails using AWS CloudTrail and Security Hub.
- Enabled SOC2-related controls using AWS Control Tower.
This setup provided a clear structure for managing users, permissions, and security across all environments.
Learn how our Migration services can help you design scalable environments and accelerate delivery — without sacrificing security or maintainability.
Milestone 3: Infrastructure and Networking
Perfsys deployed core infrastructure using Infrastructure-as-Code:
- A VPC with subnet segmentation, routing, NAT gateways, and VPN access.
- Amazon RDS for PostgreSQL replaced Cosmos DB.
- Amazon S3 buckets were used for file storage across environments.
- ALBs were configured for load balancing and HTTPS.
This setup ensured secure and scalable access to APIs, databases, and services for container-based workloads.
Milestone 4: CI/CD Automation and ECS Setup
The team automated deployments with a hybrid pipeline connected to existing Azure tooling:
- Docker images were built using Azure DevOps agents.
- Artifacts were stored in AWS ECR.
- Terraform deployed containers to Amazon ECS (EC2-backed).
- Azure Key Vault secrets were used securely within ECS tasks.
- Connections between ECS services, databases, and S3 were verified.
Milestone 5: Production Deployment
Perfsys supported the rollout of the live application in the AWS environment:
- Containers were deployed behind an internal Nginx proxy, routing traffic to microservices.
- Only VPN-based access was allowed — keeping the APIs private.
- ECS services had direct, secure access to required services: databases, object storage, APIs, and secrets.
- Safe deployment features were added, including image promotion, network isolation, and tag policies.
Results
By the end of the project, the company had a new cloud foundation with:
- A fully automated CI/CD pipeline across development, staging, and production.
- A SOC2-ready AWS setup with centralized logging and permission control.
- Private infrastructure with VPN-only access to internal resources.
- Reproducible environments managed through Terraform.
- Reduced operational workload via container orchestration and autoscaling.
- Secure handling of secrets through both Azure and AWS tools.
Developers now benefit from faster testing, reliable automation, and environments they can spin up or tear down as needed.
Conclusion
This project shows how startups with a complex engineering stack can move quickly and confidently by adopting a well-planned cloud migration strategy. With help from Perfsys, this B2B software company shifted away from rigid infrastructure and built a flexible AWS platform ready for scale and compliance.
The result is a cloud environment that supports high-velocity development and safe, secure product delivery — built to keep pace with growing demand and evolving product requirements.
FAQ
Application migration to AWS typically covers four phases: discovery and architecture mapping, AWS account and identity setup, infrastructure and networking deployment, and CI/CD automation before production cutover. The timeline depends on the number of services being moved and whether compliance controls need to be in place from day one. For this B2B software company, Perfsys completed the full migration — including SOC2-ready infrastructure — in two months. Perfsys's step-by-step migration process is designed to minimize disruption to your product team throughout.
Moving to AWS removes the environmental inconsistencies that slow down releases on less structured platforms. With Amazon ECS, ECR, and Terraform-managed infrastructure, teams get reproducible environments across development, staging, and production — meaning what works in staging ships cleanly to production. Developers on this project could spin environments up and down on demand without manual intervention. If your release cycles are constrained by infrastructure fragility, an AWS Consulting & Development engagement can identify and fix the bottlenecks.
Yes. Perfsys builds SOC2 and compliance controls into the migration itself rather than treating them as a follow-on project. This includes deploying AWS Control Tower, centralizing audit logs through CloudTrail and Security Hub, enforcing least-privilege IAM policies, and maintaining strict environment separation between production and non-production accounts. If your team is working toward SOC2, HIPAA, or ISO 27001, Perfsys's Security & Compliance service covers the AWS configuration layer end to end.
Platform decisions depend on your team's tooling, compliance needs, and the AWS services you plan to adopt. In this case, the client moved to AWS for its stronger support for container workloads via ECS, a more mature IaC ecosystem with Terraform, and compliance tooling — Control Tower and Security Hub — that simplified the SOC2 audit trail. Perfsys evaluates migration options based on your specific stack rather than a default recommendation. You can read more about how Perfsys approaches the application migration to AWS decision process on the service page.
Yes — most of Perfsys's migration clients are startups and scale-ups that have outgrown their initial cloud setup ahead of a funding round, a public launch, or a compliance deadline. The approach is scoped to what your team actually needs, without over-engineering the result. Perfsys's MVP Development Services are also available for teams that need to build on AWS from scratch rather than migrate an existing product.
Infrastructure-as-Code (IaC) means your cloud resources — VPCs, databases, load balancers, container services — are defined in version-controlled code rather than configured manually in a console. This makes environments fully reproducible, reduces configuration drift between staging and production, and simplifies compliance audits. Perfsys uses Terraform on all migrations, so every environment can be rebuilt from a known state. Combined with AWS Observability & Monitoring tooling, you also get full visibility into what those environments are doing at runtime.
Perfsys offers structured post-migration support through its AWS Managed Support Packages — covering 24/7 monitoring, incident response, cost optimization, and security updates. For teams that want to hand off cloud operations entirely, Perfsys acts as the cloud engineering function. For teams building internal capacity, Perfsys can stay involved in an advisory role. The CloudCare managed plans start from $800/month and can be adjusted or cancelled as your needs change.
Eugene Orlovsky
CEO & Founder | Serverless architect with 10+ years of hands-on experience designing cloud-native architectures on AWS, backed by multiple AWS certifications. He is writing bridges deep technical expertise with real-world business strategy, covering topics from AWS best practices to scaling tech-driven organizations.
Recommended for You
AWS Experts, On-Demand
Need to move fast? Our cloud team is ready to scale, secure, and optimize your systems. Get serverless expertise, 24/7 support, and seamless CI/CD pipelines when you need it most.
Please accept cookies to load the booking widget.