37 minutes to deploy a fullstack app on my new AWS account
Today, I was working on our Terraform Provider, and I noticed that I never tried to deploy an application from scratch on a new and clean AWS account. Meaning, an empty AWS account - with 0 resources created. No VPC, no EC2, no Load Balancer, nothing... just an IAM user to get access to my AWS account programmatically. This post explains what I did and how it took 37 minutes and 33 seconds to literally: create a VPC (10 min) create an EKS cluster and a load balancer (5 min) create an ECR repository (10 sec) deploy an RDS database (15 min) build and deploy my Django app from GitHub (2 min) add a custom domain to my app (2 min) create a TLS for my custom domain (15 sec) And tada! đ đ Let's explain all of that!
No, no... Let me explain. To deploy my full-stack app and make it available online I used the Qovery Terraform Provider. Basically, it makes AWS super easy and straightforward for anyone. No need to bother in configuring all the tiny details of each AWS resource. Behind the scene, Qovery manages all of that for us and even give us access to all the configuration. But here, I am just going to focus on the high level.
So, if we take a closer look at the terraform output we see that we have some resources that are taking more time than the others.
qovery_cluster.my_test_cluster (15 min)
This resource represents the AWS VPC and EKS creation and it takes approximately 12 to 15 minutes to create the AWS VPC.
qovery_database.psql (15 min)
This one represents the AWS RDS instance. Behind the scene, Qovery enables backup, encryption, Point In Time Recovery, and all the things that can save your back in case of data loss. We can speed up the Postgres deployment time by switching to a "container" instance instead of a "managed" one. But here, I wanted to show how long in total it takes with an RDS one.
qovery_application.backend (4 min)
This step includes:
The fetch of my app from GitHub (link here).
The build with Buildpacks.
The push in my ECR registry.
The deployment of my app on my AWS EKS (Kubernetes) cluster.
The domain and the TLS attached to my app.
It is a lot of small steps inside, but it's rather fast compared to the steps before.
Show me the result!
Here is the final result đ
Video
Screenshots
I hope you liked it!
Share on :
Tired of fighting your Kubernetes platform?
Qovery provides a unified Kubernetes control plane for cluster provisioning, security, and deployments - giving you an enterprise-grade platform without the DIY overhead.
Managing Kubernetes deployment YAML across multi-cloud enterprise fleets
At enterprise scale, managing provider-specific Kubernetes YAML across multiple clouds creates crippling configuration drift and operational toil. By adopting an agentic Kubernetes management platform, infrastructure teams abstract cloud-specific configurations (like ingress controllers and storage classes) into a single, declarative intent that automatically reconciles across 1,000+ clusters.
GPU orchestration guide: How to auto-scale Kubernetes clusters and slash AI infrastructure costs
To stop GPU costs from destroying SaaS margins, teams must transition from static to consumption-based infrastructure by utilizing Karpenter for dynamic provisioning, maximizing hardware density with NVIDIA MIG, and leveraging Qovery to tie scaling directly to business metrics.
AI is helping developers write more code, faster than ever. But writing code is only half the story. What happens after? Building, deploying, debugging, scaling. That's where teams still lose hours.We're building Qovery for this era. Not just to deploy your code, but to make everything that comes after writing it just as fast.
Alessandro Carrano
Head of Product
AI
Developer Experience
Kubernetes
 minutes
March 27, 2026
MCP Server is the future of your team's incidentâs response
Learn how to use the Model Context Protocol (MCP) to transform static runbooks into intelligent, real-time investigation tools for Kubernetes and cert-manager.
Beyond the spreadsheet: Using GitOps to generate DORA-compliant audit trails.
By adopting GitOps and utilizing management platforms like Qovery, fintech teams can automatically generate DORA-compliant audit trails, transforming regulatory compliance from a manual, time-consuming chore into an automated, native byproduct of their infrastructure.
Day 2 operations: an executive guide to Kubernetes operations and scale
Kubernetes success is determined by Day 2 execution, not Day 1 deployment. While migration is a bounded project, maintenance is an infinite loop that often consumes 40% of senior engineering capacity. To protect margins and velocity, enterprises must transition from manual toil to agentic automation that handles scaling, security, and cost.
Day-0, day-1, and day-2 Kubernetes: defining the phases of fleet management
Day-0 is planning, Day-1 is deployment, and Day-2 is the infinite lifecycle of maintenance. While Day-0/1 are foundational, Day-2 is where enterprise operational debt accumulates. At fleet scale (1,000+ clusters), managing these differences manually is impossible, requiring agentic automation to maintain stability and eliminate toil.