How aravind1314/cloud-resume works
Main Components
• Code Repository & CI/CD Pipeline: Represent the GitHub repository as the source of truth that contains the application code, Terraform configurations, Dockerfile, docker-compose file, and Jenkinsfile. Also, include GitHub Actions (as well as a reference to the Jenkinsfile if needed) as the orchestrator for the CI/CD pipeline.
• Website Application: Show the “app” directory as the web application component that includes Node.js with Express, HTML, CSS, and client-side JavaScript. Indicate that “server.js” serves the application on port 3000.
• Deployment Environment: Detail the AWS EC2 instance where the Dockerized website is deployed. Show that after provisioning, the deployment process (via SSH and execution of the “script-cmnds.sh”) installs and runs the container.
• Reverse Proxy & SSL: Represent Nginx running on the EC2 instance as the reverse proxy that forwards requests from port 80/443 to port 3000 where the Node.js app is running. Also, include Certbot for SSL certificate management.
• Optional: Infrastructure Automation Tools – also mention supporting tools like Docker Compose (indicated by the docker-compose.yaml file) used for container orchestration on the EC2 instance, and additional scripts (e.g., script.groovy, terraform/script.sh) that support automation.
Relationships and Data Flow
• From the CI/CD pipeline, branch out to two main processes:
• Finally, illustrate that the Docker container running the Node.js application is accessible via the EC2 instance and is reverse proxied through Nginx. Nginx is further configured to use Certbot for managing SSL certificates, ensuring HTTPS traffic is supported.
Architectural Patterns and Design Principles
• Infrastructure as Code (IaC): Mark the Terraform component as the “IaC” segment that ensures reproducible and reliable AWS resource provisioning.
• Containerization: Highlight the role of Docker in encapsulating the application runtime.
• Reverse Proxy & Security: Show the separation between the application server (Node.js) and the public-facing gateway (Nginx with Certbot for SSL).
Technologies & Frameworks
• Frontend & Backend: Node.js, Express, HTML/CSS/JS
• CI/CD: GitHub Actions (with reference to Jenkinsfile as an alternative branch/tool if necessary)
• Containerization: Docker, Docker Compose
• Infrastructure: Terraform alongside AWS components (EC2, VPC, etc.), with state management via S3
• Web Server & SSL: Nginx and Certbot
Instructing the Principal Software Engineer
• Clearly demarcate the phases: code commit → CI/CD workflow initiates → Infrastructure Provisioning with Terraform on AWS → Docker image build/push to Docker Hub → SSH into EC2 and deployment → Nginx configuration and SSL setup.