From ClickOps to Code: How Mission Transformed
EnterpriseDB's AWS Infrastructure with Terraform and
Centralized Networking
Executive Summary
EnterpriseDB, the leading contributor to Postgres, partnered with Mission's Cloud Crew professional services team to modernize on AWS through Infrastructure as Code and centralized networking. The engagement delivered custom Terraform solutions, an AWS Transit Gateway implementation, and end-to-end automation that transformed how EnterpriseDB operates in AWS, establishing the foundation for SOC 2 compliance while paving the way for $50,000 in annual cost savings.
About EnterpriseDB
EnterpriseDB stands as the premier seller, supporter, and contributor to Postgres worldwide. The company offers EDB Postgres AI, an integrated platform bridging traditional database utility with data warehousing and AI components, bringing data to life under one cohesive solution.
"I can't even imagine how far behind we would be if we hadn't invested in Mission when we did. Their team brought an extremely high level of experience along with a high level of enthusiasm. They produced exactly the outcomes we were looking for."
Stephan Grob,
Sr. Director of IT Infrastructure
Background
For years, EnterpriseDB had operated approximately 140 AWS accounts with no central management. Production and non-production environments didn’t have appropriate separation and were mostly created through manual console clicks over years of organic growth.
Challenge
EnterpriseDB faced critical infrastructure challenges that required modernization to support its growth trajectory. The company's 140+ AWS accounts operated as independent networks on public interfaces, a legacy of rapid expansion in the early cloud era. Every account functioned without centralized management. The core infrastructure relied on manual "ClickOps" deployments through the AWS console, making consistency difficult and scalability challenging. This approach limited opportunities for micro-segmentation and created obstacles as EnterpriseDB pursued SOC 2 certification for its services. The company needed to demonstrate mature configuration management practices while establishing consistency across deployments. Without Infrastructure as Code, Person A's deployment would differ from Person B's, creating unpredictable outcomes. As a former executive at the company observed, EnterpriseDB had transitioned from a “large small” company to a “small large” company, and practices that worked at a smaller scale no longer fit the organization's maturation goals.
Why Mission
EnterpriseDB selected Mission after discontinuing an engagement with another consulting firm that failed to meet EnterpriseDB's unique requirements. Mission's Cloud Crew team stood out by providing truly customized solutions tailored to EnterpriseDB's unique environment. The team delivered top-tier resources whose expertise and enthusiasm impressed EnterpriseDB throughout the engagement. Mission's organized approach included dedicated project management, keeping the complex engagement on track. The hands-on engineers demonstrated deep qualifications for the work, creating solutions that went beyond standard implementations to address EnterpriseDB's distinct challenges.
Why AWS
Even as EnterpriseDB maintains presence across all three major cloud providers to support customers, AWS serves as the company's primary cloud platform. The company began its cloud journey with AWS years ago, building deep operational expertise. AWS's comprehensive service portfolio supports EnterpriseDB's dual mission of selling and supporting Postgres products across diverse customer environments worldwide.
"Before Mission, my team wasn't doing any work in Terraform. Now they work in it exclusively. We’ve completely shed our former ClickOps mindset and now have custom code that makes sense for our business."
Stephan Grob,
Sr. Director of IT Infrastructure
Solution
Mission's Cloud Crew professional services team designed a comprehensive transformation centered on Infrastructure as Code and network modernization. The engagement began with analyzing EnterpriseDB's existing deployment patterns and organizational structure, then recommending improvements aligned with the company's maturation goals.
The team created custom Terraform code specifically tuned to EnterpriseDB's environment rather than generic templates. This customization proved critical for adoption, giving EnterpriseDB's infrastructure team code they could understand, modify, and extend. The solution introduced proper micro-segmentation by separating production and non-production environments into distinct accounts with appropriate network boundaries.
Mission implemented centralized networking through AWS Transit Gateway, replacing the fragmented approach where 140+ accounts each operated independent networks. This architecture eliminated public network exposure, routing all traffic through private networks accessible only via VPN. The design included centralized ingress and egress through AWS Network Firewall for improved observability and security controls.
The team delivered end-to-end automation connecting Okta, Jira, and AWS for account creation. Users request AWS accounts through Okta, triggering approval workflows and Jira ticket generation. The system automatically creates AWS accounts with proper baseline configurations and notifies requesters when resources are ready. This workflow represented novel territory, pushing boundaries while delivering practical value.
Throughout the engagement, Mission focused on knowledge transfer, ensuring EnterpriseDB's team could maintain and extend the solutions independently. The foundation enabled EnterpriseDB to enhance the code further, using the learning opportunity to build internal capabilities.
Results
Mission fundamentally transformed EnterpriseDB's infrastructure operations and security posture. The infrastructure team completely abandoned manual console operations in favor of Terraform, achieving the cultural shift sought from the beginning. Team members now approach manual deployments with genuine aversion, fully embracing Infrastructure as Code principles.
Security improvements proved substantial. Private networks accessible only through VPN replaced public interfaces, eliminating broad attack surfaces. The micro-segmentation model separates production from non-production environments, meeting requirements for SOC 2 certification pursuits. Centralized networking through Transit Gateway enables comprehensive visibility, with all ingress and egress traffic flowing through AWS Network Firewall for monitoring and control.
The automated account creation process brings remarkable efficiency. What once required manual coordination now flows seamlessly from request through Okta, approval, Jira ticketing, and AWS provisioning. Users receive notifications when accounts are ready, removing the infrastructure team from routine requests.
Financial benefits reached $50,000 in projected annual savings through network consolidation. Multiple NAT gateways scattered across 140+ accounts will consolidate to approximately 12, dramatically reducing networking costs while improving efficiency and observability.
New accounts now deploy automatically into the centralized private network. EnterpriseDB’s team continues to migrate legacy accounts, primarily by creating fresh environments rather than complex migrations. The foundation Mission built enabled EnterpriseDB to extend the code substantially, building additional modules that accelerate future deployments.
Developers gained quality-of-life improvements by eliminating troublesome bastion hosts. Direct VPN connectivity to private networks removed a persistent friction point that generated weekly complaints. The new architecture removes blockers that previously slowed productivity.
AWS Services Used
- AWS Transit Gateway
- Amazon VPC
- AWS Organizations
- AWS Identity and Access Management (IAM)
- AWS Elastic Container Registry (ECR)
- AWS Lambda
- AWS Step Functions