Amazon Web Services (AWS)

Qovery lets you quickly deploy applications to your Amazon Web Services (AWS) account. No knowledge needed, and it takes less than 20 minutes to install Qovery on your AWS account.

Do you want to know more about how Qovery works on your AWS account? Here is explained how Qovery works under the hood.

Getting started

Before you begin, this page assumes the following:

You have a Qovery account
You have created an Organization
You have an AWS account

Connect your AWS account

To link your AWS account to Qovery you need to provide an AWS access key id and secret access key with the required IAM permissions.

You can link more than one AWS account. Qovery also support multiple Cloud providers within the same Organization. Meaning, you can balance your workload on different Cloud providers. Read more.

Create your AWS credentials - `access key id` and `secret access key`

Connect to your AWS console
Go to IAM
Create Admins group without any permissions
The default name required by Qovery is Admins. If you want to use another name, you have to change the cluster advanced settings aws.iam.admin_group BEFORE launching the cluster installation process
Create one IAM user called qovery.

Setup IAM permissions to the qovery user.

Download IAM permissions JSON

Or copy it from below:

{
    "Statement": [
        {
            "Action": [
                "dynamodb:*",
                "iam:*",
                "ec2:*",
                "autoscaling:*",
                "application-autoscaling:*",
                "elasticloadbalancing:*",
                "ecr:*",
                "ecs:*",
                "eks:*",
                "rds:*",
                "elasticache:*",
                "kms:*",
                "logs:*",
                "cloudwatch:*",
                "cloudtrail:LookupEvents",
                "events:DescribeRule",
                "events:DeleteRule",
                "events:ListRuleNamesByTarget",
                "events:ListTargetsByRule",
                "events:PutRule",
                "events:PutTargets",
                "events:RemoveTargets",
                "es:AddTags",
                "es:RemoveTags",
                "es:ListTags",
                "es:DeleteElasticsearchDomain",
                "es:DescribeElasticsearchDomain",
                "es:CreateElasticsearchDomain",
                "s3:*",
                "tag:GetResources"
            ],
            "Effect": "Allow",
            "Resource": "*"
        }
    ],
    "Version": "2012-10-17"
}

Then, follow the arrows in AWS console to create AWS credentials with required IAM permissions:

To create an access key id and secret access key, go to the Security Credentials tab of the Qovery user and press Create access key
You can now save the access key id and secret access key

How was it? Did this tutorial work? Yes No

Well done!! You now have your AWS access key id and secret access key and your permissions are setups; It is time to connect Qovery to your AWS account.

Install a new cluster on Qovery

You will be able to use the credentials you just generated when creating a cluster via the Qovery console. This cluster will be linked to your Qovery organization. Follow this documentation to create a new cluster on your organization.

Deployed AWS components

Network Services	Optional	Description
A dedicated multi AZ VPC	no	Everything Qovery will deploy, will be deployed inside this VPC
Subnets, routing tables, subnet groups and security groups for RDS (multi AZ)	no	Dedicated network fand security rules for RDS
Subnets, routing tables, subnet groups and security groups for DocumentDB (multi AZ)	no	Dedicated network fand security rules for DocumentDB
Subnets, routing tables, subnet groups and security groups for Elasticache (multi AZ)	no	Dedicated network fand security rules for Elasticache
An internet gateway for the VPC	no	Required to let containers having access to Internet
Dedicated NLB to redirect 443 traffic to Nginx Ingress	no	High Availability network load balancer, pointing to Nginx Ingress inside EKS
NAT gateways (multi AZ) + EIP addresses (multi AZ) + subnet groups + routing table	yes	Useful to get outgoing static IP
Dedicated VPC routes for VPC peering	yes	Useful to perform VPC peering with others VPC on the same or different account

Kubernetes Services	Optional	Description
A dedicated EKS cluster (multi AZ) for this VPC	no	Dedicated Kubernetes cluster managed by AWS with nodes (instances type) defined by the customer
IAM dedicated user for AWS EBS CSI to access EC2 volumes + a dedicated policy	no	Required to allow EKS cluster having access to volume and mount them to containers
IAM dedicated user for AWS IAM User Sync + a dedicated policy	no	Required to sync desired IAM account to EKS to let them connect directly ot Kubernetes
IAM dedicated user for a Cluster Autoscaler+ a dedicated policy	no	Required to let autoscaler having access to EC2 autoscaling groups
IAM dedicated policies for AWS EKS CNI, EC2 container registry + EKS worker nodes	no	Required to let EKS having access to container registry and configure the Kubernetes network
Security group for EKS remote access (dual authentication: TLS + IAM authenticator)	no	Required to have a secure remote access on the Kubernetes cluster
Security group for 443 port pointing to Nginx ingress inside EKS	no	External access to web services inside the Kubernetes cluster

Other Services	Optional	Description
Cloudwatch log groups for the EKS cluster	no	Kubernetes logs, useful for the AWS and EKS support to diagnose an issue
Dedicated S3 bucket for application's logs + a dedicated IAM account	no	Application's logs are stored in an KMS encrypted S3 pivate bucket
Dedicated S3 bucket to store the kubeconfig	no	Kubernetes Kubeconfig is stored in an KMS encrypted, private and versionned bucket, used by Qovery for application's deployment

Remove Qovery from your AWS account

Your applications and your data will be deleted.

To delete Qovery from your AWS account you must be the owner of the Qovery Organization and you have to delete everything in this order:

Environments
Clusters

If you remove the access to your AWS account before deleting all the resources on the Qovery platform, you will have to manually delete them by yourself by following the guide "I don't have Qovery access anymore, how could I delete Qovery deployed resources on my AWS account?" in this section.

IAM permissions

Qovery required IAM permissions to create, update and managed the infrastructure.

IAM is used to create IAM roles
S3 is used to store our generated configuration files
Cloudwatch, for creating a group stream for each Kubernetes clusters
Autoscaling for RDS and autoscaling rules for the Kubernetes cluster
Elastic load-balancing for ELB / ALB / NLB.
DynamoDB to have a distributed lock on infrastructure deployment.
ECR for managing the container registry, create/update/delete repository.
KMS to load and store keys (RDS, SSH, …)
EKS to create and update the Kubernetes cluster.

Regions

Qovery supports the following AWS regions:

	name	description	supported
🇺🇸	us-west-2	US West (Oregon)	Yes
🇺🇸	us-east-2	US East (Ohio)	Yes
🇺🇸	us-east-1	US East (N. Virginia)	Yes
🇺🇸	us-west-1	US West (N. California)	No (Only 2 Availability Zone)
🇿🇦	af-south-1	Africa (Cape Town)	Yes
🇭🇰	ap-east-1	Asia Pacific (Hong Kong)	Yes
🇮🇳	ap-south-1	Asia Pacific (Mumbai)	Yes
🇯🇵	ap-northeast-1	Asia Pacific (Tokyo)	Yes
🇰🇷	ap-northeast-2	Asia Pacific (Seoul)	Yes
🇯🇵	ap-northeast-3	Asia Pacific (Osaka)	Yes
🇸🇬	ap-southeast-1	Asia Pacific (Singapore)	Yes
🇦🇺	ap-southeast-2	Asia Pacific (Sydney)	Yes
🇨🇦	ca-central-1	Canada (Toronto)	Yes
🇨🇳	cn-north-1	China (Beijing)	Yes
🇨🇳	cn-northwest-1	China (Ningxia)	Yes
🇩🇪	eu-central-1	Europe (Frankfurt)	Yes
🇮🇪	eu-west-1	Europe (Ireland)	Yes
🏴󠁧󠁢󠁥󠁮󠁧󠁿	eu-west-2	Europe (London)	Yes
🇫🇷	eu-west-3	Europe (Paris)	Yes
🇮🇹	eu-south-1	Europe (Milan)	Yes
🇸🇪	eu-north-1	Europe (Stockholm)	Yes
🇧🇭	me-south-1	Middle East (Bahrain)	Yes
🇧🇷	sa-east-1	South America (São Paulo)	Yes

Qovery supports regions where Amazon EKS is supported.

Manually configure VPC subnet

VPC subnet is automatically defined by Qovery on cluster creation. However, you may want to choose your own VPC subnet, for example to perform VPC Peering.

If you want to perform VPC Peering with Qovery, please refer to our guide VPC Peering with Qovery to be assisted step by step.

Have a look at [this section][docs.using-qovery.configuration.clusters#custom-vpc-subnet]] to know more on how to set the VPC Subnet.

Configure routing table

You may want to create and edit a network routing table to perform VPC peering. This can be done by accessing to the parameters of a cluster, in the settings of your organization.

If you want to perform VPC Peering with Qovery, please refer to our guide VPC Peering with Qovery to be assisted step by step.

Have a look at [this section][docs.using-qovery.configuration.clusters#network]] to know more on how to set the routing table.

How Qovery works on AWS

Qovery is an abstraction layer on top of AWS and Kubernetes. Qovery manages the configuration of AWS account, and helps you to deploy production ready apps in seconds. To make it works, Qovery rely on Kubernetes for stateless apps (containers), and AWS for stateful apps (databases, storage...).

Read more on how Qovery works behind the scene.

Kubernetes

The first time you set up your AWS account, Qovery creates a Kubernetes cluster in your chosen region. Qovery managed it for you - no action required. It takes ~15 minutes to configure and bootstrap a Kubernetes cluster. Once bootstrapped, your Kubernetes cluster runs the Qovery app and is ready to deploy your applications.

Managed services

AWS provides managed services for PostgreSQL, MySQL, Redis, MongoDB. Qovery gives you access to those services when you set the environment mode to Production. In Development mode, Qovery provides containers equivalent, which is cheaper and faster to start.

Security and compliance

Qovery runs your Kubernetes cluster and is autonomous to manage your applications, which means:

Your configuration are stored on your AWS account.
Your configuration is encrypted on your AWS account.
Qovery can't access to your data.
Suppose Qovery stops to run, your applications are not impacted.

FAQ

How to choose a region?

Different datacenters are located in different geographic areas, and you may want to keep your site physically close to the bulk of your user base for reduced latency.

I don't find a region that is provided by AWS

We are probably testing the support of this region, please contact us to know what's the status

Migrate between Cloud providers and regions

Today, you can't migrate an environment from one region to another after it has been created. Vote here if you need this feature.

#Getting started

#Connect your AWS account

#Create your AWS credentials - access key id and secret access key

#Install a new cluster on Qovery

#Deployed AWS components

#Remove Qovery from your AWS account

#IAM permissions

#Regions

#Manually configure VPC subnet

#Configure routing table

#How Qovery works on AWS

#Kubernetes

#Managed services

#Security and compliance

#FAQ

#How to choose a region?

#I don't find a region that is provided by AWS

#Migrate between Cloud providers and regions