DevOps: Set Up Automated CI/CD + Secure AWS Infrastructure

We’re building a “fire & forget” DevOps system for our startup GoPratle, an event marketplace (MERN stack).
Our goal is to create a simple, automated, and secure setup where developers push to GitHub → code auto-deploys to AWS (staging or production), with safe secrets, cost optimization, and no long-term DevOps dependency.

Scope of Work;

*Audit current setup: Review GitHub Actions, AWS EC2, IAM, MongoDB, and existing deployment structure.

*Set up CI/CD:
-staging branch → auto-deploy to staging EC2.
-main branch → manual or approved deploy to production (protected PR).

*Secrets Management:
-Use GitHub Secrets for CI/CD, AWS Secrets Manager for runtime secrets.
-Connect via OIDC (no static AWS keys).

*Server & Security:
-Enable AWS Session Manager (no PEM keys).
-Create IAM roles for staging/production EC2 with least privilege.
-Separate staging_db in MongoDB cluster (staging user only).
-Optimize cost – auto-stop staging instance when idle.

*Monitoring & Backups:
-Basic CloudWatch setup + daily snapshot automation.

*Documentation & Handover:
-Write simple onboarding & runbook docs (how to add/remove devs, rotate secrets, trigger deploys).
-30–45 min live walkthrough at handover.


Deliverables:

-Fully automated GitHub Actions pipeline (staging + production).
-Secure secrets system (GitHub + AWS).
-SSM-based access (no PEM keys).
-Cost-optimized staging setup with backups & rollback.
-Onboarding & DevOps Runbook documentation.
-Post-handover support for issues.

Tech Stack : GitHub Actions · AWS EC2 · IAM · Secrets Manager · MongoDB Atlas · Node.js · React · Cashfree · CloudWatch