Terraform-Driven EKS Microservice Deployment
Budget: ₹1,500 – ₹12,500 INR
I need a complete, reproducible path that starts with infrastructure as code and ends with a live microservice running in AWS EKS.
Here is what I want built:
• Terraform from scratch – clean, modular code that provisions a production-ready EKS cluster (no other AWS resources are required right now).
• Jenkins-based CI/CD – the pipeline must be locked down with best-practice credentials handling, branch-based triggering, and automated rollback on failed deployments.
• Kubernetes manifests/Helm charts – whatever is cleaner – so my containerised microservice can be rolled out, scaled and rolled back easily.
Acceptance will be straightforward:
1. I run terraform init/plan/apply and the cluster stands up with zero manual tweaks.
2. A push to the main branch kicks Jenkins, builds the image, pushes it, and updates the workload in EKS.
3. A quick kubectl get pods shows the new revision healthy.
Feel free to recommend naming conventions, remote state back-ends, or additional safeguards; I just want the pipeline solid and the code readable.
Here is what I want built:
• Terraform from scratch – clean, modular code that provisions a production-ready EKS cluster (no other AWS resources are required right now).
• Jenkins-based CI/CD – the pipeline must be locked down with best-practice credentials handling, branch-based triggering, and automated rollback on failed deployments.
• Kubernetes manifests/Helm charts – whatever is cleaner – so my containerised microservice can be rolled out, scaled and rolled back easily.
Acceptance will be straightforward:
1. I run terraform init/plan/apply and the cluster stands up with zero manual tweaks.
2. A push to the main branch kicks Jenkins, builds the image, pushes it, and updates the workload in EKS.
3. A quick kubectl get pods shows the new revision healthy.
Feel free to recommend naming conventions, remote state back-ends, or additional safeguards; I just want the pipeline solid and the code readable.