Introduction

In the world of DevOps, automation is key to ensuring that deployments are repeatable, efficient, and free from human error. Recently, I completed a project where I automated the deployment of a Node.js application on AWS using Ansible. This application allows users to input their name, email, and upload a profile picture. The application then stores the photo in an S3 bucket and the name and email in an RDS MySQL database.
In this blog post, I'll walk you through the project, the challenges I faced, and the key learnings I gained along the way.
 - -

Project Overview

The primary goal of this project was to automate the deployment of a Node.js application on AWS. The application handles user data by storing profile pictures in S3 and user information in RDS. The deployment was automated using Ansible, a powerful tool for Infrastructure as Code (IaC).
Tech Stack:

• Frontend: Node.js
• Backend: AWS RDS, S3
• Automation Tool: Ansible
• Deployment Platform: AWS EC2
• Web Server: NGINX  - -

Deployment Process

1. Setting Up the EC2 Instance
To begin, I launched an EC2 instance using AWS and configured security groups to allow HTTP/HTTPS traffic. This instance served as the host for the application.
2. Deploying the Node.js Application
Next, I uploaded the Node.js application to the EC2 instance. I used Vite as the build tool, which provided a fast and optimized development experience. After building the app for production, I installed the necessary dependencies and prepared the environment for deployment.
3. Installing and Configuring NGINX
NGINX was installed on the EC2 instance to serve the Node.js application. The server was configured to act as a reverse proxy, forwarding requests to the application.
This configuration ensures that all incoming requests are routed correctly to the Node.js application.
4. Automating with Ansible
The entire deployment process was automated using Ansible. I created Ansible playbooks to:

• Provision the EC2 instance
• Set up and configure the S3 bucket and RDS MySQL database
• Deploy the Node.js application
• Install and configure NGINX
• Set up environment variables and manage application secrets using a .env file Ansible roles were used to modularize the tasks, making the automation process more efficient and scalable.  - -

Challenges and Solutions

1. Environment Configuration:
**Configuring the environment variables correctly was critical to ensuring that the application could securely connect to the AWS services. I used Ansible to create a .env file with the necessary credentials and connection strings.
**2. AWS Service Integration:
Integrating the application with AWS RDS and S3 required careful handling of permissions and network settings. Ansible made it easier to manage these configurations across different environments.
3. NGINX Configuration:
Setting up NGINX to serve the nodejs application required configuring it as a reverse proxy. Debugging issues with the NGINX configuration was a key learning experience, particularly in managing static files and ensuring that all routes were correctly handled.
4. Ansible playbook:
Setting up ansible playbook to configure the app for performing the applications backend configuration automatically. Ansible playbook runs on the Master server and performs or executes the program in the worker servers in this case only one server.
Check out the complete documentation and the codes in my GitHub Repo.
 - -

Key Learnings

1. Ansible for Automation:
This project deepened my understanding of Ansible's capabilities in automating complex deployments. By structuring the playbooks and roles correctly, I was able to create a reusable and scalable automation process.
2. AWS Integration:
Gaining hands-on experience with AWS services like EC2, S3, and RDS was invaluable. Understanding how to securely integrate these services with an application is a crucial skill in modern cloud development.
3. Infrastructure as Code (IaC):
The project reinforced the importance of IaC principles, allowing for consistent and repeatable deployments across different environments.
 - -

Conclusion and Future Plans

Automating the deployment of this Node.js application on AWS was a challenging yet rewarding experience. The project provided me with a deeper understanding of both cloud infrastructure and automation tools. Moving forward, I plan to explore more advanced CI/CD pipelines and enhance the application's features and security.
Interested in the technical details? You can find the full documentation and playbooks in my GitHub repository. If you have any questions or would like to discuss the project further, feel free to connect with me!