June 2022 Summaries

Qovery's DevOps automation software streamlines the process of deploying applications on AWS, empowering over 20,000 developers to autonomously manage their applications across development, staging, and production environments. In June, Qovery introduced several noteworthy features, including Slack integration for real-time notifications, advanced settings accessible via API, and Kubernetes probes for application health checks. They also implemented auto-scaling based on CPU metrics and offered customization options for network settings. A significant development is the introduction of Qovery EC2, a cost-effective $20/month solution for hosting applications on AWS, suitable for development and hobby projects, distinguishing it from the pricier AWS EKS service. Additionally, Qovery's V3 product update promises enhanced developer experience and is set for Alpha testing, reflecting a year's worth of user feedback and development efforts.

In response to the initial launch of the V2 console in September 2021, which provided essential features for developers, the V3 console introduces significant enhancements aimed at improving user experience, transparency, and integration. The V3 console focuses on a smoother onboarding process with detailed guidance, increased transparency with comprehensive insights into infrastructure usage, costs, and event history, and convenient access to infrastructure logs for debugging. It also expands integration capabilities, supporting tools like Slack, Datadog, and GitHub Actions. The console has transitioned from Angular to React to better accommodate future recruitment needs. The V3 console offers essential features such as environment and service management, application and database overviews, and infrastructure logs. Open-source and accessible, the V3 console is set for an Alpha soft launch at the end of June, with plans to collect user feedback for a September Beta release that will include all features available in V2.

Familiarizing developers and DevOps professionals with Terraform and AWS, the document outlines how to utilize Qovery for building robust infrastructure on AWS, sharing best practices and ready-to-use architecture for various projects. It provides an example of deploying an application with a PostgreSQL database on AWS across three environments: Production, Staging, and Development, each running in dedicated VPCs. The text explains the Terraform setup for creating clusters and environments, detailing the resources involved, such as Kubernetes clusters, Qovery environments, and projects, and highlights the process of deploying a Strapi application and PostgreSQL databases using AWS services like RDS and ECR. Additionally, it describes how Qovery automates the creation of necessary infrastructure components, manages secrets and environment variables, and deploys applications and databases in parallel, enabling the setup of a comprehensive, multi-environment architecture on AWS in under two hours with the help of Terraform and Qovery.

Qovery Preview Environments offer significant advantages for engineering teams by enhancing DevOps efficiency, improving development speed, and reducing costs. These environments allow for the automation of complex production-like environments, enabling rapid setup and teardown which accelerates time to market. They facilitate isolated testing of individual pull requests without interference, promoting faster development cycles and quicker release times. Costs are controlled by automating environment updates and cleanups, with the ability to set expiration times for inactive environments. The process for creating a Preview Environment involves establishing a "blueprint" environment, enabling deployment features, validating the blueprint, and then creating and deleting Preview Environments as needed. Future guides are set to expand on integrating these environments with CI platforms and other advanced features, making them a versatile tool for scalable and cost-effective application development.

The guide provides instructions on setting up Slack integration with Qovery, an application deployment platform. It includes a demo video showcasing how Qovery functions in conjunction with Slack to enhance user experience. The documentation encourages users to try the integration to streamline communication and workflow between these platforms.

AWS is a popular choice for startups due to its flexibility and range of services, but it requires some level of DevOps expertise, which is where Qovery comes into play. Qovery provides a simplified, Heroku-like experience for building and managing AWS infrastructure, eliminating the need for in-house DevOps skills while maintaining AWS's reliability. By using Qovery, users can set up AWS infrastructure quickly and effortlessly deploy and scale applications using Kubernetes (EKS) clusters, all while retaining complete control and visibility over AWS costs. Qovery functions as an abstraction layer on top of tools like Kubernetes, Terraform, and Helm, and provides a production-ready platform layer without impacting the underlying infrastructure. The step-by-step process detailed shows how a production-ready AWS infrastructure can be established in under 30 minutes, highlighting Qovery's potential to help companies quickly scale their operations and reduce time to market.

The text provides a comprehensive guide on implementing JWT authentication and authorization in a Spring Boot application, using a demo project available on GitHub. The guide explains the structure of a JSON Web Token (JWT), which is composed of a header, payload, and signature, and outlines how these tokens are used to authenticate and authorize users by storing claims such as username, roles, and token expiration. It describes the use of Spring Security's abstract classes to configure endpoint security and the creation of a JwtRequestFilter to manage authentication by checking the presence of a JWT in request headers. The document also introduces the concept of an API Token at the organization level, offering persistent access without the need for repeated JWT generation, and discusses how to generate, hash, and validate these tokens while ensuring they can be revoked if necessary. The implementation details include using SecureRandom for generating random strings, CRC32 for integrity checks, and hashing functions for secure storage of tokens. The guide highlights the advantages of using JWTs and API Tokens for application security and provides testing instructions to verify the setup, emphasizing the simplicity and security benefits of this approach.