Operations | Monitoring | ITSM | DevOps | Cloud

Hi, fellow Qovery readers, Albane here! 👋 To give you a bit of background, I joined Qovery in August 2021, initially as a Product Owner, then moved to a Product Marketing Manager position in March 2022. So yes, I’m all about our product. However, I also spend much time learning about our partner’s products, and that’s why, on April 27, 2022, I spent the day at the ExCel Centre in London to attend the annual AWS Summit.

We are in May 2022, and hundreds of startups have built their infrastructure on AWS using Qovery. This article will share the 10 best (and fancy) AWS architectures our customers have made. From the most classic architecture to the craziest 🤪 It can give you some ideas. Let's go 🚀

AWS ELB (Elastic load balancer) automatically distributes incoming application traffic across multiple targets and virtual appliances in one or more Availability Zones (AZs). That helps you achieve high availability and fault tolerance. In this article, we will share with you some tips that will help you best utilize AWS load balancer. We will also provide insights on the best use cases of ALB and NLB, which are the two most commonly used load balancers.

In 2020, my co-founders and I had this crazy idea of bringing a better Developer Experience on top of AWS. You know, the one that you can easily use with "the promise of the cloud" that any developer can take advantage of and deploy their next successful product in seconds. Somehow, the missing product of AWS 😅. This is where Netlify was an excellent source of inspiration. A nice Developer Experience, where deploying an application is as simple as pushing your code on Git.

Using containers for microservices has gained a lot of popularity in the last decade or so. Developing the application through microservices across multiple containers results in the best of both worlds. It provides resilience as well as agility through scaling and improvements. Before we dwell on how containers and microservices form an ideal combination, let’s start with a basic understanding of microservices and containers.

During the past two weeks, our Frontend and Backend teams were busy bees 🐝 with a particular sprint dedicated to bug hunting �� and improvements! Yes, both of the two weeks sprints were dedicated to bugs and improvements ONLY: tracking them, then solving them; gotta catch ‘em all 🚀

Amazon Elastic Container Service (Amazon ECS) is a fully managed container orchestration service that makes it easy for you to deploy, manage and scale containerized applications. Although ECS is a managed service and hides many complexities under the hood, there have been many cases where startups have not been able to take full advantage of ECS due to slow deployments. In this article, we will share some tips to improve deployment speed on ECS. We will try to cover both EC2 tasks and Fargate tasks.

Containers are superior to Virtual Machines (VM) in many aspects, including the benefits of being lightweight, easily scalable, highly portable, etc. AWS provides two primary container services i.e., Amazon Elastic Container Service (Amazon ECS) and Amazon Elastic Kubernetes Service (EKS). Although both ECS and EKS are growing in popularity but achieving security while using these services is relatively a new topic.

This is the second part of our EKS with Terraform series. In Part 1, we talked about Infrastructure as Code and its benefits. We also mentioned the tools we will be using. This time we will actually start using Terraform to create a VPC and EC2 instance.