End-to-End DevOps Pipeline Build

I need a complete DevOps workflow that begins with code pushed to GitHub and ends with a fully deployed, container-based application in AWS. Both Jenkins and GitHub Actions should be wired up so that either service can trigger the build; this dual setup lets me keep legacy jobs in Jenkins while experimenting with the lighter GitHub-native approach.

For each pipeline, automated testing, deployment steps, and monitoring/notification stages must be included. On success, the workflow should package the application into Docker images, push them to a registry, and roll them out to a Kubernetes cluster.

Infrastructure has to be declared in Terraform. At minimum it should provision VPC, subnets, security groups, EC2 nodes (worker/group where necessary), and S3 buckets that store state or artifacts. Everything should be expressible in code and reproducible with a single terraform apply.

Nginx will front the web service, so please include a clean, easily parameterised config that supports blue-green or rolling updates. Version control and collaboration will happen in a GitHub repo; branch protection rules and a clear PR workflow are expected.

Optional but welcome: integrate CloudWatch dashboards or an equivalent solution so I can view deployment metrics and pipeline logs in one place.

Deliverables
1. Jenkinsfile and GitHub Actions workflow files covering automated tests, deployment stages, and notifications.
2. Terraform modules/workspace layouts for VPC, EC2, S3, and security groups, committed to the repo.
3. Dockerfiles plus Kubernetes manifests/Helm charts that handle container creation, management, and orchestration.
4. Nginx configuration ready for drop-in use behind a load balancer.
5. GitHub repository set up with branch policies and example pull request template.
6. Step-by-step documentation: setup prerequisites, how to run pipelines locally, how to promote to prod, and rollback instructions.
7. (Optional) CloudWatch or equivalent monitoring templates integrated with the above.

Acceptance criteria
• A merged PR triggers the full pipeline in both Jenkins and GitHub Actions without manual intervention.
• terraform plan shows no drifts when run after a successful deploy.
• kubectl get pods returns healthy containers running the new image.
• Nginx serves the application on the intended domain and path.
• All documentation builds cleanly and matches the delivered infrastructure.

I’m happy to clarify edge cases or AWS account details once you’re ready to begin.