The latest articles on DEV Community by Raj Dhumal (@rajd810). https://dev.to/rajd810 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4241548%2Fbdb3fccc-3841-4c88-9ca4-a51998358987.jpg https://dev.to/rajd810 en Raj Dhumal Thu, 12 Nov 2026 17:44:57 +0000 https://dev.to/rajd810/how-we-migrated-from-aws-api-gateway-to-kong-konnect-using-cdktf-and-azure-devops-1g89 https://dev.to/rajd810/how-we-migrated-from-aws-api-gateway-to-kong-konnect-using-cdktf-and-azure-devops-1g89 <p>Recently, I got an opportunity to work on an interesting project where we migrated our APIs from AWS API Gateway to Kong Konnect.</p> <p>One thing we wanted to improve during this migration was how we managed API configurations and deployments.</p> <p>Earlier, managing configurations manually wasn't the approach we wanted to continue with. So, we decided to move towards Infrastructure as Code (IaC) and automate the entire process as much as possible.</p> <p>For this, we used CDKTF (Terraform with TypeScript) to manage Kong configurations and Azure DevOps to handle deployments.</p> <p>Here's a little about what we did and some of the challenges we came across.</p> <p><strong>What did we implement?</strong></p> <p>We wanted to manage everything through code instead of depending on manual UI configurations.</p> <p><strong>Here's how we approached it:</strong></p> <ul> <li>Created Kong services, routes and plugins using CDKTF.</li> <li>Managed Dev, Stage and Production environments using a common codebase.</li> <li>Built Azure DevOps pipelines to automate Terraform deployments.</li> <li>Implemented a Plan → Approval → Apply workflow so changes could be reviewed before deployment.</li> <li>Worked on a rollback approach using previously maintained Terraform state and configuration</li> </ul> <p><strong>What challenges did we face?</strong></p> <p>Like any migration project, things weren't always straightforward. We came across a few challenges along the way:</p> <ul> <li>Authorization: Mapping existing AWS API Gateway authorizers to the corresponding Kong plugins.</li> <li>Rate Limiting: Making sure rate-limiting configurations worked as expected after migration.</li> <li>Authentication: Handling existing authentication configurations in Kong.</li> <li>Zero Downtime: Planning the migration carefully to avoid any service interruption.</li> </ul> <p>Each of these required proper validation and testing to make sure the APIs continued to work as expected.</p> <p><strong>What did we like about this approach?</strong></p> <p>For me, the biggest improvement was the way we started managing infrastructure.</p> <p>A few things that made a real difference:</p> <ul> <li>Everything was maintained in Git and became version-controlled.</li> <li>No more dependency on manually configuring APIs through the UI.</li> <li>Deployments became more consistent across environments.</li> <li>Changes could be reviewed before applying them.</li> <li>Managing configurations became much easier with a common codebase.</li> </ul> <p>My takeaway</p> <p>One thing I really liked about this project was seeing how much difference Infrastructure as Code can make in day-to-day operations.</p> <p>Instead of spending time on repetitive manual configurations, we could focus more on automation, consistency and making the deployment process reliable.</p> <p>It was a great learning experience working with Kong Konnect, CDKTF, Terraform and Azure DevOps, especially when it came to API management and automation.</p> <p>I'd love to hear from others who have worked on similar migrations.</p> <p>Have you migrated from AWS API Gateway to Kong Konnect? What challenges did you face?</p> <h1> DevOps #AWS #Kong #Terraform #CDKTF #AzureDevOps #APIManagement #CloudArchitecture </h1> cdktf aws apigateway terraform