In this article, the author demonstrated how to deploy a SonarQube Server on an EC2 instance with an external database such as Amazon RDS or Aurora instead of keeping the database self-hosted within the server.
The author explained why extending SonarQube's database to an external service like RDS or Aurora is beneficial, including scalability, reliability, security, and maintenance.
The infrastructure consists of components such as VPC, internet gateway, security group, EC2 instance, NAT gateway, RDS PostgreSQL database instance, IAM role, and Secret Manager.
The author also provided the code snippet for creating the database construct in CDK and highlighted how to allow communication between the database and EC2 instance server.
The stack update included the creation of a new user data script to connect to the external database and data migration.
Finally, the author showed how to deploy the stack using the CDK command line tools and concluded the article.
This article is a good reference guide for those who want to deploy a SonarQube Server on AWS with an external database such as RDS or Aurora.
The article also highlights the benefits of using an external database service rather than keeping it self-hosted within the server, including scalability, reliability, security, and maintenance.
The code snippet provided for creating the database construct in CDK is helpful for those who are new to AWS CDK.
The step-by-step instructions provided in the article make it easy to follow and deploy the stack on AWS.