Forem: Romaric P.

Stress testing Karpenter with EKS and Qovery

Romaric P. — Tue, 02 Apr 2024 06:46:59 +0000

Let’s unroll my tweet (yes, I’m not over saying Tweet even with X), where I stressed Karpenter with EKS and Qovery.

⚠️ This is a stress test where I spent 1:30 hour; it’s not a benchmark. I’ll probably run some benchmarking to compare with Kubernetes node-autoscaler at some point, but not today :)

Setup

30 environments
Each environment: 3 containerized apps + 2 container databases (Redis and Postgres) with EBS storage
1 EKS cluster with Karpenter deployed with Qovery

If you’re not familiar with Karpenter — watch my quick intro. But in a nutshell, Karpenter is a better node autoscaler for Kubernetes (say goodbye to wasted compute resources). It is open-source and built by the AWS team. Qovery is an Internal Developer Platform I’m a co-founder) that we’ll use to spin up our EKS cluster with Karpenter.

Let’s see how things behaved.

30 Environments Deployed

I created and deployed my 30 environments — and we can see that my apps are scheduled on my cluster. The EC2 nodes are dynamically allocated to the cluster (we can see t3.smallinstances). I don’t even have to choose the instance type. Karpenter is smart to choose the right instance depending on the following criteria:

The workload of my apps
The instance types available
The best choice in terms of performance vs. costs

It’s truly a game-changer!

Note also that I’ve requested to allocate spot instances. (configurable via Qovery cluster interface)

Dynamic Node Allocation

I changed the CPU and RAM of one app from my env-1 environment to see how Karpenter will reallocate resources.

From: 250m CPU and 256 MB RAM
To: 2000m CPU and 8GB RAM

It just works nicely, and we can see that Karpenter scheduled a t3a.xlarge instance to handle my app requirement.

Cluster Scaled Down

If you are familiar with the default Kubernetes node autoscaler — you know how hard it is to downscale your cluster. For many reasons that I’ll not enumerate here… But in the case of Karpenter. It just works once again!

I stopped all my environments, and as expected, my cluster is down-scaled in less than 10 minutes as well. So I don’t have wasted resources!

Cluster Scaled Up.. Again

I wanted to see the cluster scaling up from 3 nodes to x nodes and see how fast it was... In less than 15 minutes, I got all my nodes provisioned and my 30 environments up and running.
Use Cases

At Qovery, we have hundreds of customers running testing environments with our Preview Environment product. Karpenter will solve many issues that they were facing previously. Just to mention a few...

No need to allocate a specific node pool size now
Cluster Scale-down is well handled, and no more resources are wasted (reducing AWS costs)

Interested in giving it a shot? Sign up to Qovery and create your EKS cluster with Karpenter :)

Kubernetes for Developers

Romaric P. — Sat, 13 Jan 2024 17:02:53 +0000

In the last 8 years, Kubernetes has emerged as the standard for orchestrating containerized applications. However, its complexity can be a barrier for many developers.

Disclaimer: I'm a co-founder of Qovery - but I guarantee it's not a trap! Give it a try to Qovery if you want a very nice developer experience on top of your Kubernetes cluster.

Enter Qovery - an Internal Developer Platform that can be installed on any Kubernetes cluster to bring a delightful and simplified developer experience. But don't take my word for granted. In this quick step-by-step article, I will show you how to deploy one of my GitHub apps and a Postgres database on my Kubernetes cluster running on GCP. And what's really really cool is that I don't even need to understand how Kubernetes work!

Qovery: A Brief Overview

What is Qovery?
An Internal Developer Platform that abstracts Kubernetes complexities, empowering developers to focus on their code.

Key Benefits:

Fast and easy installation on any Kubernetes cluster.
Intuitive open-source interfaces (Web, CLI, API, Terraform Provider) for efficient app deployment and
No Kubernetes expertise is required for developers.
Highly customizable for Platform Engineers.
No YAML to write for Developers ;)
Generous free plan (no credit card required).

Who Uses Qovery?

Over 60,000 developers and Platform Engineers, valuing its simplicity and efficiency.

Deploying an Application on Kubernetes with Qovery

Step 1: Set Up Your Qovery Account

Connect to console.qovery.com and sign in with GitHub, GitLab, or Bitbucket.

Then, give a name to your Organization and Choose the Free plan.

Once your organization is created, you should get this view:

I recommend familiarizing yourself with the basic concepts of Qovery to understand what an organization, cluster, project, or environment is.

Step 2: Connect Your GitHub Repository

You can skip this part if you signed up with your GitHub account. Otherwise, you can connect your GitHub account and permit Qovery to get access to your public and/or private repositories.

Go to your Organization settings > Git repositories access > then, pick the option you want to connect your GitHub account.

Step 3: Install Qovery on Your Kubernetes Cluster

To install Qovery on your Kubernetes cluster, you need to add a cluster into the Qovery interface:

Add your Kubeconfig:

Qovery will give you the commands and the generated helm configuration files you can download.

Then, you need to run the following on your Kubernetes cluster:

helm repo add qovery https://helm.qovery.com
helm repo update

helm upgrade --install -n qovery -f values-zXXX.yaml qovery

Congrats! 🥳 Your cluster is connected to Qovery. You can now deploy your apps.

Step 4: Deploy Your Application

Now, we can deploy our GitHub app on our Kubernetes cluster. Check out this short video and look how fast it is.

Here is what I did:

I created an Environment and then I created an Application.
I select my app from my GitHub repository
By default Qovery picks the Dockerfile at the root of my project but I can change it.
I set the CPU to 250m and the RAM to 256 MB
I declared my app port to be 5555 and I tick the expose publicly option -> So my app can be accessible from outside.
I deployed my app and it's accessible publicly (end of video)

This is pretty cool, right? It's not over! 😎

Step 5: Manage and Monitor Your Application

Qovery provides everything you need to manage (start, stop, restart, redeploy, delete) and check out your applications logs - directly streamed from your Kubernetes cluster. Yes!

You want to use Datadog or any third-party solutions? No problem.. Everything compatible to Kubernetes is compatible to Qovery.

Step 6: Leverage Advanced Qovery Features

I'm pretty sure you ask yourself, ok that's great all of that. But what about configuring your environment variables, your custom domain or even deploy a database... Well it's all covered :)

Imagine, you can even securely connect to your database with the Qovery CLI 😎

~ $ qovery auth
Opening your browser, waiting for your authentication...
Info: Success

~ $ qovery port-forward -p 5556:5555
Info: Current context:
Organization | MyOrg
Project      | URL Shortener
Environment  | prod
Service      | DB
Type         | database


Info: Continue with port-forward command using this context ?
Please type "yes" to validate context: yes

Listening on 127.0.0.1:5432 => 5432

~ $ psql $DATABASE_URL

psql >

Powerful out-of-the-box features

Here are a list of cool features you get out of the box:

Auto-deploy: if I do commit and push a change on my GitHub app - it will be automatically redeployed without any downtime
Clone: this is my favorite feature! You can clone your app (or your complete environment) in one click. So, testing a new feature without impacting the original app is easily possible.
Ephemeral Environment: For each Pull Request that I open for my app, Qovery will spin up a new environment
RBAC, GitHub Actions (CI/CD) integration, Logs, Deployment pipeline, env var interpolation, env var as a file, helm deployment, multiple clusters...

There are so many cool features that I could write 10 other posts to talk about them exclusively. It's probably something that I'll do if you are interested to learn more about some of them :)

Conclusion

Qovery demystifies Kubernetes for developers, making it accessible and manageable without requiring deep expertise. Feel free to try it now on your Kubernetes cluster - it's free and will always be!

If you like the Qovery web interface - give a star ⭐ - it's open source and coded in React ✨

Additional Resources:

Deploy on AWS for FREE - Claim Your $1000 Credits Today!

Romaric P. — Sat, 18 Mar 2023 17:51:36 +0000

Are you working on a side project and looking for a hassle-free way to deploy it on AWS? Look no further! I have some fantastic news for you. Qovery, an AWS partner, is offering up to $1000 in AWS credits to developers like you. In this article, we'll explore how you can benefit from these credits and deploy your apps with ease using Qovery.

Why Qovery?

Promo time 🤗 - but I promise it's not too boring. Keep reading

As developers, we often dread the process of deploying our applications, especially when it comes to dealing with complex infrastructure and configuration. Qovery aims to eliminate those headaches by providing a delightful developer experience. With Qovery, you don't need any prior AWS knowledge - just a valid Dockerfile, and you're good to go!

Qovery is trusted by more than 45,000 developers worldwide, and here's why:

Simplified Deployment Process: Qovery allows you to deploy your frontend, backend, and even databases without worrying about the underlying infrastructure.
Dockerfile Compatibility: All you need is a valid Dockerfile, and Qovery takes care of the rest.
AWS Partnership: As an AWS partner, Qovery offers up to $1000 in credits to help you kick-start your side projects on the AWS platform.

Eligibility Criteria

To benefit from this fantastic offer, there's just one simple criterion you need to meet:

You must have a valid custom email domain (no Gmail, no Outlook, etc.). The domain must also have a landing page (even a small one) explaining your project.

That's it!

Get Your $1000 AWS Credits

Ready to deploy your side project on AWS for free? Here's how you can claim your $1000 AWS credits with Qovery:

Sign Up: Register for a Qovery account using your GitHub, GitLab, or Bitbucket credentials.
Apply for the Credits: Complete a simple application form, providing details about your side project and ensuring you meet the eligibility criteria. (Check out your mailbox)
Await Approval: Once your application is reviewed and approved, your $1000 AWS credits will be added to your account.
Start Deploying: Use your credits to deploy your apps on AWS using Qovery's simplified deployment process.

FAQ

What's the catch?

We know what you might be thinking - what's the catch? Well, there isn't one! Qovery is an ISV AWS Partner, and since they work with numerous companies worldwide, AWS has granted them the ISV Activate Partner status. This allows Qovery to provide free credits to developers with serious side projects, like yours. It's a win-win situation - you get to deploy your side projects on AWS for free, and Qovery gets to help passionate developers like you bring their ideas to life.

Do I need a credit card?

For Qovery: No, you don't!
For AWS: You'll probably need one just to activate your account. But you'll not be charged for the first $1000.

Let's go?

Don't miss out on this fantastic opportunity to deploy your side projects on AWS for free with Qovery. Claim your $1000 AWS credits, and join the growing community of developers who are already reaping the benefits of Qovery's delightful developer experience. Give your side projects the boost they deserve and focus on what you love - coding.

Happy deploying!

17 Best DevOps Tools to Use in 2022 for Infrastructure Automation and Monitoring

Romaric P. — Wed, 17 Aug 2022 22:10:35 +0000

You must adopt proper infrastructure automation if you want to enable your teams to achieve faster application delivery while eliminating human errors. Automation of servers, deployment environments, configuration management, and deployments play a vital role in getting a competitive advantage for your product. Monitoring both the infrastructure and application is equally important as well.
In this article, we will discuss top tools for infrastructure automation and monitoring.

Let’s start with Infrastructure as Code (IaC) and Configuration Management.

Infrastructure as Code / Configuration Management

Infrastructure as code (IaC) allows you to provision your cloud infrastructure automatically. Whether it is VMs, databases, cloud networks, security, etc., you can create a JSON or YAML template mentioning all the details and then use it as a blueprint for creating similar environments automatically. Configuration management, on the other hand, does not target the provisioning of any of the infrastructure. It manages the server configuration of a cluster of servers and makes sure that server configuration is automatically maintained in all the servers in the server cluster. Whereas Infrastructure-as-Code automates the infrastructure, configuration management automates the configuration of the servers. Let’s review some of the top tools for IaC and configuration management.

1. Terraform

Terraform is a vendor-independent infrastructure provisioning tool. It is owned by Hashicorp. It can be used for the automatic creation of any of the cloud services, including networks, services, firewalls, databases, etc. Terraform is so popular because it is not tied to any particular cloud vendor, so you can easily move from one cloud to another. It is open source and has great community support. Terraform code is written in its own domain-specific language called HCL, which means it has a slight learning curve.

2. Pulumi

Pulumi is also an IaC tool that is similar to terraform. You can provision almost every cloud service using Pulumi. Pulumi has an advantage over Terraform in terms of testing and building the scripts. Unlike Terraform, Pulumi allows you to write its code in any of the modern programming languages like python, java, typescript, etc. That gives you better support for debugging and testing. However, the community support for Pulumi is small as compared to terraform.
Want to know what you should use between Terraform and Pulumi? Read our comparison guide

3. Ansible

Ansible is a powerful configuration management tool that is used to automate versioned software component installation, OS configuration tasks, network and firewall configuration, etc. If you have separate sets of servers for staging and production, for example, then ansible can help you write scripts that can be used to automate and manage the server configuration for each of these sets. Ansible scripts are written in Yaml.

Continuous Integration

Continuous integration is the practice of frequently combining and merging different developers’ code so that the application build could be tested as often as possible. As soon as you commit the code, the build process runs and creates the build for testing. Some of the best tools for continuous integration are the following:

4. CircleCI

CircleCI is a CI/CD platform that helps you build and run build pipelines. Through CircleCI, you can automate the building and testing of your application on every commit. It has a modern and very user-friendly interface. It supports many complex build pipelines. It has both free and paid versions available.

5. Github Actions

While many companies are already using Github for code hosting, they were looking for the existing code repository to support its own integrated CI/CD workflow. Github Actions is a powerful feature that lets you build, test and deploy your application across different platforms. If you already use Github as your source code repository, your top choice for continuous integration would be Github actions.

6. Gitlab CI

Gitlab CI is also a powerful tool for continuous integration. Like Github actions, it uses YAML files and supports docker. The auto DevOps feature of Gitlab helps users with different tasks, including building and testing applications, detecting the code language, deploying the application, and scanning for vulnerabilities.

Deployment tools

After the continuous integration of code is done, the next step is continuous deployment and delivery. Let’s review some of the best tools for continuous delivery/deployment, which take care of not just the deployment automation but infrastructure automation as well.

7. Harness

Harness is a modern software delivery platform. After the continuous integration is done on your code and the build is ready, Harness will take the build artifacts from “build” stage to “production”. It runs as a SaaS, supports a GitOps style of development, hooks into your Git repository, and has secret management as well. It has excellent integrations with Kubernetes. Harness takes the artifacts, and Kubernetes manifests you provide and deploys them to the desired Kubernetes cluster.

8. CodeFresh

Codefresh is an all-in-one solution that implements the whole code pipeline from start to finish. It handles all the aspects of DevOps, from the moment the commit is created until it is deployed to production. It has a powerful set of plugins that includes Helm and many other popular CI/CD tools like Jenkins. It has native support for Kubernetes clusters, not only for deploying applications but also for running pipelines on Kubernetes too.

9. Helm

Helm is a Kubernetes deployment manager to automate your application’s creation, packaging, configuration, and deployment to Kubernetes clusters. Managing Kubernetes YAML manifest files, even for simple deployment, can be time-consuming and error-prone. Helm makes life easier by creating a single package that can be deployed to your Kubernetes cluster.

10. Kubernetes

Kubernetes automates the deployment and operations of cloud-native applications at scale. It is the best open-source container orchestration tool in the market. Kubernetes automates container deployments across different infrastructure environments and makes sure all the resources are utilized efficiently.

Environment-as-Service

Environment as service (EaaS) is an emerging category and adopted by many DevOps teams. Through EaaS, you can quickly deploy and facilitate pre-configured environments easily and on demand. On-demand environment is the core of EaaS. An on-demand environment is a full fledge deployment environment that can be provisioned automatically through EaaS. Automatic provisioning of the environment can help you market your product faster, improve mutual collaboration between team members and take your product to the next level through rapid release cycles.

11. Qovery

Qovery has built a modern platform to deploy on-demand environments on AWS in just a few seconds. Through the “Clone” environment feature, you can create an on-demand replica of your staging, UAT, production, or any other environment with great simplicity. Another killing feature is the Preview Environments, where you can automatically get a replica of your production environment (including applications, databases, and configuration) on every pull request, so you can test your changes confidently without affecting your production.

Config/Secret Management

Securing your configuration is a crucial aspect of secure SDLC. Here are some top tools for saving your environment variables and configuration in a secure form.

12. Doppler

Doppler is a multi-cloud SecretOps Platform used by developers and security teams to manage their application secrets in a secure manner. It serves as a central source of truth for secrets and app configuration. It supports docker, serverless, and all the cloud vendors. It is the first choice by developers if your application has secrets to be organized by microservices, CI/CD, and multi-cloud deployment platforms.

13. Vault

Vault is a Secret Manager from Hashicorp, the same company behind Terraform. It has an extensive list of integrations, primarily focusing on authentication and secret storage. It is key-value-based secure storage, and you can secure access to tokens, passwords, certificates, encryption keys, etc.

Infrastructure Monitoring

Find below some of the top tools for keeping an eye on your cloud infrastructure:

14. Grafana

Grafana is an open-source platform for observability and data visualization. It allows you to view your cloud services, infrastructure, and networks through a user-friendly dashboard available online and accessible across all devices.

15. Datadog

Datadog is a proprietary SaaS-based analytics and monitoring tool for the DevOps teams. With Datadog, teams can determine performance metrics and event monitoring for your cloud-based infrastructure. Like Grafana, Datadog also supports Kubernetes monitoring.

16. Newrelic

Newrelic is also a SaaS tool that monitors the performance and availability of your applications and infrastructure. Newrelic also provides real-time monitoring of your application. It is the ideal choice if you want detailed performance monitoring of your cloud-based application.

17. Prometheus

Prometheus is a monitoring tool for your cloud-native environments. It is used for event monitoring and alerting. It is open source and has strong support for Kubernetes monitoring. It is one of the easiest and simpler tools for monitoring your infrastructure and applications.
Conclusion

Infrastructure automation is key to success for every DevOps team. It is not easy to pick an infrastructure automation and monitoring tool best suited for your needs. Many factors like cost, skillset, features, UI/UX, etc. play a decisive role in choosing the right tool for your business. The best choice is not to use just one tool. Instead, use a combination of tools suited to your needs.

At Qovery, we also use many tools as part of the DevOps suite. These include the following:

Infrastructure as Code: Terraform
CI/CD: GitHub Actions, Gitlab CI
Deployment tools: Helm, Kubernetes
Environment as a Service: Qovery
Secret Management: Vault, AWS KMS
Observability & Monitoring: Datadog, Grafana (including Loki & Promtail), Prometheus (including Alertmanager)

Deploy Strapi on AWS with Terraform and Qovery

Romaric P. — Fri, 24 Jun 2022 20:42:33 +0000

I recorded a video to show how to deploy a Strapi application on AWS. It's even simpler than the official way via the strapi documentation since I am using Terraform and Qovery (open-source).

Complete Strapi Terraform template

Deploy an app on AWS with GitHub, Qovery and Terraform

Romaric P. — Sun, 19 Jun 2022 14:09:40 +0000

This ready to use tutorial show you how to deploy an application from GitHub on AWS and make it accessible via HTTPS. All of that in just a few lines of Terraform file.

Behind the scene

Behind the scene, Qovery will:

Create a full Kubernetes infrastructure on your AWS account (VPC, Security Groups, Subnet, EKS...)
Create Qovery resources:
1. Organization Terraform Demo
2. Project URL Shortener
3. Environment production
4. Application web app
Build the web app application
Push the web app container image in your ECR registry
Deploy it on your EKS cluster (created by Qovery)
Create an AWS Network Load Balancer
Generate a TLS certificate for your app
Expose publicly via HTTPS your application

It will take approximately 20 minutes to create your infrastructure and less than 5 minutes to deploy your application.

How to use

Clone this repository
Sign in to Qovery
Install the Qovery CLI and generate an API Token with this guide.
Generate your AWS credentials (Access Key ID and Secret Access Key) with this guide
Open you terminal and run the following command by changing the values:

export TF_VAR_aws_access_key_id=YOUR_AWS_ACCESS_KEY_ID \
TF_VAR_aws_secret_access_key=YOUR_AWS_SECRET_ACCESS_KEY \
TF_VAR_qovery_access_token=YOUR_QOVERY_API_TOKEN \
TF_VAR_qovery_organization_id=YOUR_QOVERY_ORG_ID

Clone my URL Shortener application
Edit the main.tf file and change https://github.com/evoxmusic/ShortMe-URL-Shortener.git with yours
You can now run the Terraform commands

terraform init

terraform plan

terraform apply

Open your Qovery console to find out the HTTPS URL of your deployed app.
To tear down your infrastructure and avoid unnecessary cloud costs you can run terraform destroy.

And here is what happened when running terraform apply

terraform apply

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated
with the following symbols:
  + create

Terraform will perform the following actions:

  # qovery_application.backend will be created
  + resource "qovery_application" "backend" {
      + auto_preview                   = false
      + build_mode                     = "BUILDPACKS"
      + buildpack_language             = "PYTHON"
      + built_in_environment_variables = [
        ] -> (known after apply)
      + cpu                            = 500
      + environment_id                 = (known after apply)
      + environment_variables          = [
          + {
              + id    = (known after apply)
              + key   = "DEBUG"
              + value = "false"
            },
          + {
              + id    = (known after apply)
              + key   = "PORT"
              + value = "3333"
            },
        ]
      + git_repository                 = {
          + branch    = "main"
          + root_path = "/"
          + url       = "https://github.com/evoxmusic/ShortMe-URL-Shortener.git"
        }
      + id                             = (known after apply)
      + max_running_instances          = 1
      + memory                         = 256
      + min_running_instances          = 1
      + name                           = "backend"
      + ports                          = [
          + {
              + external_port       = 443
              + id                  = (known after apply)
              + internal_port       = 3333
              + protocol            = "HTTP"
              + publicly_accessible = true
            },
        ]
      + state                          = "RUNNING"
    }

  # qovery_aws_credentials.my_aws_creds will be created
  + resource "qovery_aws_credentials" "my_aws_creds" {
      + access_key_id     = (sensitive value)
      + id                = (known after apply)
      + name              = "URL Shortener"
      + organization_id   = "67df37d8-6139-42eb-8c60-452395d12222"
      + secret_access_key = (sensitive value)
    }

  # qovery_cluster.my_cluster will be created
  + resource "qovery_cluster" "my_cluster" {
      + cloud_provider    = "AWS"
      + credentials_id    = (known after apply)
      + description       = "Terraform demo cluster"
      + features          = {
          + vpc_subnet = (known after apply)
        }
      + id                = (known after apply)
      + instance_type     = "T3A_MEDIUM"
      + max_running_nodes = 4
      + min_running_nodes = 3
      + name              = "Demo cluster"
      + organization_id   = "67df37d8-6139-42eb-8c60-452395d1c2ab"
      + region            = "us-east-2"
      + state             = "RUNNING"
    }

  # qovery_environment.production will be created
  + resource "qovery_environment" "production" {
      + built_in_environment_variables = [
        ] -> (known after apply)
      + cluster_id                     = (known after apply)
      + id                             = (known after apply)
      + mode                           = "DEVELOPMENT"
      + name                           = "dev"
      + project_id                     = (known after apply)
    }

  # qovery_project.my_project will be created
  + resource "qovery_project" "my_project" {
      + built_in_environment_variables = [
        ] -> (known after apply)
      + description                    = (known after apply)
      + id                             = (known after apply)
      + name                           = "URL Shortener"
      + organization_id                = "67df37d8-6139-42eb-8c60-452395d1c2ab"
    }

Plan: 5 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

qovery_aws_credentials.my_aws_creds: Creating...
qovery_aws_credentials.my_aws_creds: Creation complete after 0s [id=d2cfe19d-6381-4676-99e6-6721182f0c4c]
qovery_cluster.my_cluster: Creating...
qovery_cluster.my_cluster: Still creating... [10s elapsed]
qovery_cluster.my_cluster: Still creating... [20s elapsed]
qovery_cluster.my_cluster: Still creating... [30s elapsed]
qovery_cluster.my_cluster: Still creating... [40s elapsed]
qovery_cluster.my_cluster: Still creating... [50s elapsed]
qovery_cluster.my_cluster: Still creating... [1m0s elapsed]
qovery_cluster.my_cluster: Still creating... [1m10s elapsed]
qovery_cluster.my_cluster: Still creating... [1m20s elapsed]
qovery_cluster.my_cluster: Still creating... [1m30s elapsed]
qovery_cluster.my_cluster: Still creating... [1m40s elapsed]
qovery_cluster.my_cluster: Still creating... [1m50s elapsed]
qovery_cluster.my_cluster: Still creating... [2m0s elapsed]
qovery_cluster.my_cluster: Still creating... [2m10s elapsed]
qovery_cluster.my_cluster: Still creating... [2m20s elapsed]
qovery_cluster.my_cluster: Still creating... [2m30s elapsed]
qovery_cluster.my_cluster: Still creating... [2m40s elapsed]
qovery_cluster.my_cluster: Still creating... [2m50s elapsed]
qovery_cluster.my_cluster: Still creating... [3m0s elapsed]
qovery_cluster.my_cluster: Still creating... [3m10s elapsed]
qovery_cluster.my_cluster: Still creating... [3m20s elapsed]
qovery_cluster.my_cluster: Still creating... [3m30s elapsed]
qovery_cluster.my_cluster: Still creating... [3m40s elapsed]
qovery_cluster.my_cluster: Still creating... [3m50s elapsed]
qovery_cluster.my_cluster: Still creating... [4m0s elapsed]
qovery_cluster.my_cluster: Still creating... [4m10s elapsed]
qovery_cluster.my_cluster: Still creating... [4m20s elapsed]
qovery_cluster.my_cluster: Still creating... [4m30s elapsed]
qovery_cluster.my_cluster: Still creating... [4m40s elapsed]
qovery_cluster.my_cluster: Still creating... [4m50s elapsed]
qovery_cluster.my_cluster: Still creating... [5m0s elapsed]
qovery_cluster.my_cluster: Still creating... [5m10s elapsed]
qovery_cluster.my_cluster: Still creating... [5m20s elapsed]
qovery_cluster.my_cluster: Still creating... [5m30s elapsed]
qovery_cluster.my_cluster: Still creating... [5m40s elapsed]
qovery_cluster.my_cluster: Still creating... [5m50s elapsed]
qovery_cluster.my_cluster: Still creating... [6m0s elapsed]
qovery_cluster.my_cluster: Still creating... [6m10s elapsed]
qovery_cluster.my_cluster: Still creating... [6m20s elapsed]
qovery_cluster.my_cluster: Still creating... [6m30s elapsed]
qovery_cluster.my_cluster: Still creating... [6m40s elapsed]
qovery_cluster.my_cluster: Still creating... [6m50s elapsed]
qovery_cluster.my_cluster: Still creating... [7m0s elapsed]
qovery_cluster.my_cluster: Still creating... [7m10s elapsed]
qovery_cluster.my_cluster: Still creating... [7m20s elapsed]
qovery_cluster.my_cluster: Still creating... [7m30s elapsed]
qovery_cluster.my_cluster: Still creating... [7m40s elapsed]
qovery_cluster.my_cluster: Still creating... [7m50s elapsed]
qovery_cluster.my_cluster: Still creating... [8m0s elapsed]
qovery_cluster.my_cluster: Still creating... [8m10s elapsed]
qovery_cluster.my_cluster: Still creating... [8m20s elapsed]
qovery_cluster.my_cluster: Still creating... [8m30s elapsed]
qovery_cluster.my_cluster: Still creating... [8m40s elapsed]
qovery_cluster.my_cluster: Still creating... [8m50s elapsed]
qovery_cluster.my_cluster: Still creating... [9m0s elapsed]
qovery_cluster.my_cluster: Still creating... [9m10s elapsed]
qovery_cluster.my_cluster: Still creating... [9m20s elapsed]
qovery_cluster.my_cluster: Still creating... [9m30s elapsed]
qovery_cluster.my_cluster: Still creating... [9m40s elapsed]
qovery_cluster.my_cluster: Still creating... [9m50s elapsed]
qovery_cluster.my_cluster: Still creating... [10m0s elapsed]
qovery_cluster.my_cluster: Still creating... [10m10s elapsed]
qovery_cluster.my_cluster: Still creating... [10m20s elapsed]
qovery_cluster.my_cluster: Still creating... [10m30s elapsed]
qovery_cluster.my_cluster: Still creating... [10m40s elapsed]
qovery_cluster.my_cluster: Still creating... [10m50s elapsed]
qovery_cluster.my_cluster: Still creating... [11m0s elapsed]
qovery_cluster.my_cluster: Still creating... [11m10s elapsed]
qovery_cluster.my_cluster: Still creating... [11m20s elapsed]
qovery_cluster.my_cluster: Still creating... [11m30s elapsed]
qovery_cluster.my_cluster: Still creating... [11m40s elapsed]
qovery_cluster.my_cluster: Still creating... [11m50s elapsed]
qovery_cluster.my_cluster: Still creating... [12m0s elapsed]
qovery_cluster.my_cluster: Still creating... [12m10s elapsed]
qovery_cluster.my_cluster: Still creating... [12m20s elapsed]
qovery_cluster.my_cluster: Still creating... [12m30s elapsed]
qovery_cluster.my_cluster: Still creating... [12m40s elapsed]
qovery_cluster.my_cluster: Still creating... [12m50s elapsed]
qovery_cluster.my_cluster: Still creating... [13m0s elapsed]
qovery_cluster.my_cluster: Still creating... [13m10s elapsed]
qovery_cluster.my_cluster: Still creating... [13m20s elapsed]
qovery_cluster.my_cluster: Still creating... [13m30s elapsed]
qovery_cluster.my_cluster: Still creating... [13m40s elapsed]
qovery_cluster.my_cluster: Still creating... [13m50s elapsed]
qovery_cluster.my_cluster: Still creating... [14m0s elapsed]
qovery_cluster.my_cluster: Still creating... [14m10s elapsed]
qovery_cluster.my_cluster: Still creating... [14m20s elapsed]
qovery_cluster.my_cluster: Still creating... [14m30s elapsed]
qovery_cluster.my_cluster: Still creating... [14m40s elapsed]
qovery_cluster.my_cluster: Still creating... [14m50s elapsed]
qovery_cluster.my_cluster: Still creating... [15m0s elapsed]
qovery_cluster.my_cluster: Still creating... [15m10s elapsed]
qovery_cluster.my_cluster: Still creating... [15m20s elapsed]
qovery_cluster.my_cluster: Still creating... [15m30s elapsed]
qovery_cluster.my_cluster: Still creating... [15m40s elapsed]
qovery_cluster.my_cluster: Still creating... [15m50s elapsed]
qovery_cluster.my_cluster: Still creating... [16m0s elapsed]
qovery_cluster.my_cluster: Still creating... [16m10s elapsed]
qovery_cluster.my_cluster: Still creating... [16m20s elapsed]
qovery_cluster.my_cluster: Still creating... [16m30s elapsed]
qovery_cluster.my_cluster: Still creating... [16m40s elapsed]
qovery_cluster.my_cluster: Still creating... [16m50s elapsed]
qovery_cluster.my_cluster: Still creating... [17m0s elapsed]
qovery_cluster.my_cluster: Still creating... [17m10s elapsed]
qovery_cluster.my_cluster: Still creating... [17m20s elapsed]
qovery_cluster.my_cluster: Still creating... [17m30s elapsed]
qovery_cluster.my_cluster: Still creating... [17m40s elapsed]
qovery_cluster.my_cluster: Still creating... [17m50s elapsed]
qovery_cluster.my_cluster: Still creating... [18m0s elapsed]
qovery_cluster.my_cluster: Still creating... [18m10s elapsed]
qovery_cluster.my_cluster: Creation complete after 18m12s [id=782f5b71-5786-4ff6-895a-277cd432dc1e]
qovery_project.my_project: Creating...
qovery_project.my_project: Creation complete after 0s [id=2fa442d0-f798-46f8-9a1a-b33317c507ea]
qovery_environment.production: Creating...
qovery_environment.production: Creation complete after 0s [id=8418d920-c508-4ea2-b669-72b1fedc3a3e]
qovery_application.backend: Creating...
qovery_application.backend: Still creating... [10s elapsed]
qovery_application.backend: Still creating... [20s elapsed]
qovery_application.backend: Still creating... [30s elapsed]
qovery_application.backend: Still creating... [40s elapsed]
qovery_application.backend: Still creating... [50s elapsed]
qovery_application.backend: Still creating... [1m0s elapsed]
qovery_application.backend: Still creating... [1m10s elapsed]
qovery_application.backend: Still creating... [1m20s elapsed]
qovery_application.backend: Still creating... [1m30s elapsed]
qovery_application.backend: Still creating... [1m40s elapsed]
qovery_application.backend: Still creating... [1m50s elapsed]
qovery_application.backend: Still creating... [2m0s elapsed]
qovery_application.backend: Still creating... [2m10s elapsed]
qovery_application.backend: Still creating... [2m20s elapsed]
qovery_application.backend: Creation complete after 2m23s [id=8dd99960-939c-4328-9a38-fdea20d7db8a]

Apply complete! Resources: 5 added, 0 changed, 0 destroyed.

I hope you liked it!

The ultimate guide to migrate from Heroku to AWS in 1 hour

Romaric P. — Sat, 21 May 2022 12:41:27 +0000

This guide describes how to migrate your application running on Heroku to AWS with Qovery. It covers all required steps you need to take to deploy your application on AWS and transfer your data from Heroku Postgres to the database managed by AWS.

Qovery is a platform used by more than 22 000 developers to deploy their apps on their AWS account. It's the "Heroku-like" experience on top of AWS.

This is the final result 😎

Assumptions 👨‍🏫

You have an application on Heroku
You are familiar with Heroku basics, have a Heroku account and access to Heroku CLI
You have sign in on Qovery
You have set up your AWS account with Qovery

Costs 💵

Qovery installs an EC2 instance (perfect for hobby project) or an EKS cluster (perfect for production) on your AWS account.
Qovery is free up to 100 deployments/month (see pricing)

Migration Steps 🪜

Use Buildpacks or Create your Dockerfile
Create resources on Qovery
Configure Environment Variables and Secrets
Copy data from your Heroku databases to your AWS databases
Deploy your apps
FAQ by Heroku users

1. Create your Dockerfile or Use Buildpacks 🍃

Qovery supports two ways to build and run your application coming from Heroku:

Buildpacks
Docker

Both options build a container image that is runnable by a container engine (E.g. Docker). Qovery runs containers on Kubernetes.

I will explain how to use Buildpacks. Refer to the original guide to get instructions to use a Dockerfile.

Buildpacks automatically detects the language and the framework your application is using. Buildpacks builds and runs your app. Here is the list of supported languages and frameworks.

Supported languages

language	version
Node.JS	any
Clojure	any
Python	any
Java	any
Gradle	any
JVM	any
Grails	any
Scala	any
Play	any
PHP	any
Go	any

⚠️ We do recommend using Docker to keep the full control of what's going on behind the scene. Buildpacks is a great technology but difficult to debug when something goes wrong. You can try deploying your apps on AWS with Qovery with Buildpacks, if you do not succeed, we do recommend switching for Docker.

Limitations 👀

Here are some limitations due to our Buildpacks implementation:

Qovery Buildpacks does not support Procfile with multiple commands at the moment.
Qovery does not support custom Buildpacks.

Those limitations will be solved in the coming months.

2. Create resources on Qovery 👩‍💻

Application

Steps:

Connect to the Qovery console.
Create your Organization and your Project.
Create an environment with the name production (it can be changed after).
Create an application and give it a name (you can give the name of your repo if you have no idea)
Select your app repository from your GitHub, GitLab or Bitbucket.
Select the branch you want to deploy.
Select the Build mode for Buildpacks or Dockerfile according to what you want.
Specify the local listening port of your application.
Click on "create"

Congrats! Your application is created 🎉

⚠️ Your application is created but not deployed yet! You can configure the vCPU, Memory, Environment Variables... before deploying it. If you want to deploy it before finishing the configuration you can click on "Actions" > "Deploy".

If you deploy an app from a mono-repository, we have a must-read guide for you here.

Database ⚡️

Here are the steps to deploy your database:

Steps:

Go to your production environment.
Add your database by clicking on "Add" > "Database".
Select the database (PostgreSQL, MySQL, MongoDB, Redis..) and the version you want to deploy.
Select Managed or Container mode for your database.
Select Public accessibility (set Private if you don't want to restore your data from an existing Heroku database).

Congrats! Your database is created as well 🎉

If you use MongoDB Atlas, or an existing database on AWS that you want to connect to your application deployed by Qovery. Check out our tutorial about VPC peering and how to securely connect to your existing database.

3. Configure your Environment Variables and Secrets 🛡

Qovery makes the difference between an Environment Variable and a Secret. Basically, a Secret is similar to an Environment Variable but the value is encrypted and can't be revealed. Both are injected as environment variables during the build and the run of your applications.

To extract your environment variables from Heroku, we recommend using the Heroku CLI and exporting all the environment variables and secrets in an .env (dot env) file. Qovery supports the import of a dot env file via the Qovery web interface and the Qovery CLI.

⚠️ If you use Buildpacks for one of your app AND you have indicated a local listening port of your application, you will need to add an environment variable PORT with the value of your port to make your application starting properly. Otherwise, Qovery will fail to deploy your app!

Export your environment variable via the Heroku CLI with the command:

# To install Heroku CLI: https://devcenter.heroku.com/articles/heroku-cli
heroku config

GREETINGS: hello world
STRIPE_API_KEY: xxx-yyy-zzz
IS_PRODUCTION: true

Then you can create your environment variables via the web interface (watch the video below)

Or via the Qovery CLI:

# auth yourself
qovery auth

# selection the app where you want to import your environment variables
qovery context set

# import your Heroku environment variables
heroku config --app <your_heroku_app_name> --json | qovery env import --heroku-json

Qovery: Heroku environment variables import from JSON
? Do you want to import Environment Variables or Secrets? Environment Variables
? What environment variables do you want to import?  [Use arrows to move, space to select, <right> to all, <left> to none, type to filter]
  [x]  GREETINGS=hello world
  [ ]  STRIPE_API_KEY=xxx-yyy-zzz
> [x]  IS_PRODUCTION=true

Qovery: ✅ Environment Variables successfully imported!

⚠️ Import sensitive data (E.g. API keys, credentials...) as Secret and not Environment Variable.

Connect your frontend app to your backend app

To connect your frontend app your backend app we will create an [environment variable alias][docs.using-qovery.configuration.environment-variable#alias-environment-variable].

Here is how to create a frontend app:

And now how to connect your frontend app with your backend app:

You can also take a look at this forum reply to learn how to do it.

Connect your backend app to your database

Same as connecting your frontend app to your backend app, you can create an environment variable alias DATABASE_URL for the built-in secret finishing with _DATABASE_URL_INTERNAL.

⚠️ Create an alias on _DATABASE_URL_INTERNAL and not _DATABASE_URL

4. Copy data from your Heroku databases to your AWS databases

Coming soon with Replibyte

5. Deploy your apps!

We are finally ready to deploy my applications on AWS!

Watch the final result 😎

https://www.loom.com/share/da31c21f9c104eae9270e4c4db59055e

FAQ by Heroku users

How to create a custom domain?

Check out the documentation on how to configure your custom domain.

How to monitor my apps?

We do recommend using Datadog or any other monitoring products for monitoring your apps deployed by Qovery. Check out our tutorial on how to install Datadog

Do you have Heroku "Review App" equivalent?

Yes, it's what we call Preview Environment

Is it possible to get a shell / connect to my app?

Yes, with the Qovery CLI and the command qovery shell. Check out the documentation.

Can I use Terraform and Infrastructure as Code?

Absolutely, we have a Qovery Terraform provider available.

How can I connect my app to MongoDB Atlas?

If you use MongoDB Atlas check out our tutorial about VPC peering and how to securely connect to your existing MongoDB Atlas database.

How can I connect my app to an AWS service not managed by Qovery?

If you want to connect your app to an AWS service not managed by Qovery, check out our tutorial about VPC peering and how to securely connect to this AWS service.

If you have a common question about Qovery, we have a more general FAQ section available.

Wrapping up 👋🏼

Congrats! You have migrated from Heroku to AWS. Feel free to check out our forum and open a thread if you have any question.

The top 10 AWS architecture built with Qovery in 2022

Romaric P. — Sun, 01 May 2022 06:41:52 +0000

We are in May 2022, and hundreds of startups have built their infrastructure on AWS using Qovery. Check out this guide where I share the 10 best (and fancy) AWS architectures our users have made.

https://www.qovery.com/blog/the-top-10-aws-architecture-built-with-qovery-in-2022

A tool to seed your dev database with real data

Romaric P. — Thu, 28 Apr 2022 05:20:48 +0000

A bunch of developers and myself have created RepliByte - an open-source tool to seed a development database from a production database.

Features ⚡

Support data backup and restore for PostgreSQL, MySQL and MongoDB
Replace sensitive data with fake data
Works on large database (> 10GB) (read Design)
Database Subsetting: Scale down a production database to a more reasonable size
Start a local database with the prod data in a single command
On-the-fly data (de)compression (Zlib)
On-the-fly data de/encryption (AES-256)
Fully stateless (no server, no daemon) and lightweight binary
Use custom transformers

My motivation

As a developer, creating a fake dataset for running tests is tedious. Plus, it does not reflect the real-world data and painful to keep updated. If you prefer to run your app tests with production data. Then RepliByte is for you as well.

Available for MacOSX, Linux and Windows.

https://github.com/qovery/replibyte give a ⭐ if you like it.

How to seed your dev Postgres DB with your prod DB with RepliByte

Romaric P. — Thu, 31 Mar 2022 22:17:15 +0000

Intro

In my company, we build a platform for developers to help them deploying easily their apps on AWS. One major feature that we have is the Preview Environment - which let any developer to create a full replica environment from the production for every pull request. It's convenient and we had to find a way to clone the apps and the databases with the data included. That's why I created RepliByte - an open-source tool written in Rust to synchronize cloud databases and hide sensitive data 🔥

Backup your prod Postgres DB into S3

source:
  connection_uri: $DATABASE_URL
  encryption_key: $MY_PRIVATE_ENC_KEY # optional 
bridge:
  bucket: $BUCKET_NAME
  access_key_id: $ACCESS_KEY_ID
  secret_access_key: $AWS_SECRET_ACCESS_KEY

To run the backup

replibyte -c prod-conf.yaml backup run

To list your backups

replibyte -c prod-conf.yaml backup list

type          name                    size    when                    compressed  encrypted
PostgreSQL    backup-1647706359405    154MB   Yesterday at 03:00 am   true        true
PostgreSQL    backup-1647731334517    152MB   2 days ago at 03:00 am  true        true
PostgreSQL    backup-1647734369306    149MB   3 days ago at 03:00 am  true        true

Clean sensitive data

RepliByte provides the Transformers to clean up the sensitive data from your database.

# Transformers

Here is a list of all the transformers available.

| id              | description                                                                                        | available |
| --------------- | -------------------------------------------------------------------------------------------------- | --------- |
| transient       | Does not modify the value                                                                          | yes       |
| random          | Randomize value but keep the same length (string only). [AAA]->[BBB]                               | yes       |
| first-name      | Replace the string value by a first name                                                           | yes       |
| email           | Replace the string value by an email address                                                       | yes       |
| keep-first-char | Keep only the first char for strings and digit for numbers                                         | yes       |
| phone-number    | Replace the string value by a phone number                                                         | yes       |
| credit-card     | Replace the string value by a credit card number                                                   | yes       |
| redacted        | Obfuscate your sensitive data (>3 characters strings only). [4242 4242 4242 4242]->[424**********] | yes       |

To use the Transformers, you need to edit your configuration file and add them:

source:
  connection_uri: $DATABASE_URL
  encryption_key: $MY_PRIVATE_ENC_KEY # optional 
  transformers:
    - database: public
      table: employees
      columns:
        - name: last_name
          transformer_name: random
        - name: birth_date
          transformer_name: random-date
        - name: first_name
          transformer_name: first-name
        - name: email
          transformer_name: email
        - name: username
          transformer_name: keep-first-char
    - database: public
      table: customers
      columns:
        - name: phone
          transformer_name: phone-number
bridge:
  bucket: $BUCKET_NAME
  access_key_id: $ACCESS_KEY_ID
  secret_access_key: $AWS_SECRET_ACCESS_KEY

Then your sensitive data will be hidden while seeding your dev Postgres DB 👌

Seed your dev Postgres DB

To restore a backup, you first need to declare a destination in your YAML config file.

bridge:
  bucket: $BUCKET_NAME
  access_key_id: $ACCESS_KEY_ID
  secret_access_key: $AWS_SECRET_ACCESS_KEY
destination:
  connection_uri: $DATABASE_URL
  decryption_key: $MY_PUBLIC_DEC_KEY # optional

Then, you need to run replibyte backup list to list all the backup available

replibyte -c prod-conf.yaml backup list

type          name                    size    when                    compressed  encrypted
PostgreSQL    backup-1647706359405    154MB   Yesterday at 03:00 am   true        true
PostgreSQL    backup-1647731334517    152MB   2 days ago at 03:00 am  true        true
PostgreSQL    backup-1647734369306    149MB   3 days ago at 03:00 am  true        true

and replibyte restore to seed your dev database

replibyte -c prod-conf.yaml restore -v latest

OR 

replibyte -c prod-conf.yaml restore -v backup-1647706359405

What else?

RepliByte is written in Rust and all operations are made on the fly. Meaning no extra disk space is consumed and there is no data leak risk. ⚡️
RepliByte also supports MongoDB (Thanks to Benny - contributor) 🔥
Complete data synchronization 💪🏼
Work on different any cloud providers 🌍
You can use multiple transformers to hide your sensitive data 🙈
Designed to backup TB of data 🏆
Skip data sync for specific tables 👌
On-the-fly data (de)compression (Zlib) and de/encryption (AES-256)🛡

Conclusion

RepliByte is a command line tool that makes database seeding super easy and convenient. I am working on a way to restore a database locally with Docker in one command. More is coming so stay tuned and feel free to share your feedback.

RepliByte GitHub: https://github.com/Qovery/replibyte

RepliByte - an open-source tool to synchronize PostgreSQL in multiple environments

Romaric P. — Thu, 24 Mar 2022 23:15:27 +0000

After months of experimenting with different ways of synchronizing databases, I am super excited to announce RepliByte - an open-source tool to synchronize cloud databases and fake sensitive data - This tool is written in Rust.

As explained in the README, my primary motivation is to respond to a widespread need that most developers have - cloning the production database into a development database while cleaning the sensitive data. It is precisely the purpose of RepliByte.

I am still in the early days of development, but you can look at the code and the README. It should be clear enough to help me out in that journey, and why not contribute?!

RepliByte supports PostgreSQL, MySQL and MongoDB supports is in progress by the community 😎.

I freshly recorded this short demo explaining what is RepliByte and how to use it.

Happy to have your feedback.
RepliByte is written in Rust and we are looking for contributors.

Blazingly Fast Preview Environments for Temporal on Kubernetes

Romaric P. — Thu, 17 Mar 2022 21:18:37 +0000

Temporal.io is a workflow engine that able to coordinate microservices and can be developed by writing code and we can use its parts over and over again with a modular architecture.

One engineer from my team has written this tutorial explaining how to deploy multiple environments of Temporal on a Kubernetes cluster This tutorial explains how to get one temporal instance per environment.

Note: consider using Temporal namespaces if you do not want to spawn a full temporal cluster per environment.

Happy reading.

Forem: Romaric P.

Stress testing Karpenter with EKS and Qovery

30 Environments Deployed

Dynamic Node Allocation

Cluster Scaled Down

Cluster Scaled Up.. Again

Kubernetes for Developers

Qovery: A Brief Overview

Deploying an Application on Kubernetes with Qovery

Step 1: Set Up Your Qovery Account

Step 2: Connect Your GitHub Repository

Step 3: Install Qovery on Your Kubernetes Cluster

Step 4: Deploy Your Application

Step 5: Manage and Monitor Your Application

Step 6: Leverage Advanced Qovery Features

Powerful out-of-the-box features

Conclusion

Deploy on AWS for FREE - Claim Your $1000 Credits Today!

Why Qovery?

Eligibility Criteria

Get Your $1000 AWS Credits

FAQ

What's the catch?

Do I need a credit card?

Let's go?

17 Best DevOps Tools to Use in 2022 for Infrastructure Automation and Monitoring

Infrastructure as Code / Configuration Management

1. Terraform

2. Pulumi

3. Ansible

Continuous Integration

4. CircleCI

5. Github Actions

6. Gitlab CI

Deployment tools

7. Harness

8. CodeFresh

9. Helm

10. Kubernetes

Environment-as-Service

11. Qovery

Config/Secret Management

12. Doppler

13. Vault

Infrastructure Monitoring

14. Grafana

15. Datadog

16. Newrelic

17. Prometheus

Deploy Strapi on AWS with Terraform and Qovery

Deploy an app on AWS with GitHub, Qovery and Terraform

Behind the scene

How to use

The ultimate guide to migrate from Heroku to AWS in 1 hour

Assumptions 👨‍🏫

Costs 💵

Migration Steps 🪜

1. Create your Dockerfile or Use Buildpacks 🍃

Limitations 👀

2. Create resources on Qovery 👩‍💻

Application

Database ⚡️

3. Configure your Environment Variables and Secrets 🛡

Connect your frontend app to your backend app

Connect your backend app to your database

4. Copy data from your Heroku databases to your AWS databases

5. Deploy your apps!

FAQ by Heroku users

How to create a custom domain?

How to monitor my apps?

Do you have Heroku "Review App" equivalent?

How to rollback?

How auto-scaling works?

How to manage database migration?

Is it possible to get a shell / connect to my app?

Can I use Terraform and Infrastructure as Code?

How can I connect my app to MongoDB Atlas?

How can I connect my app to an AWS service not managed by Qovery?

Wrapping up 👋🏼

The top 10 AWS architecture built with Qovery in 2022