AWS EC2 Jenkins Pipeline
Budget / SalaryHourly project
TypeFreelance project
LocationRemote
Posted2 hours ago
I am ready to move a production-bound web application onto AWS and want a clean, automated path from commit to deployment. The target runtime is Amazon EC2, and Jenkins is the continuous-integration engine I would like driving the process.
Here is what I need from you:
• A complete CI/CD pipeline that triggers on pushes to my Git repository, runs automated tests, builds an artifact, and pushes it to EC2 with zero-downtime or minimal-downtime deployment logic.
• Secure, repeatable AWS infrastructure for the pipeline itself—whether that is spun up through CloudFormation, Terraform, or another infrastructure-as-code approach you recommend.
• Parameterised Jenkins jobs (or a Jenkinsfile) with clear environment variables so I can promote the same build through dev, staging, and production.
• Automated rollback steps in case a deployment fails.
• Documentation I can hand to another engineer or use myself to modify the pipeline later.
The web application is already container-ready, but if you see a simpler path that still lands on EC2, I am open to suggestions. Other AWS native tools such as CodePipeline or Lambda can be mentioned in your proposal if they reduce maintenance, but Jenkins on EC2 is my baseline requirement.
Please include in your response:
– A brief outline of the steps you will take to deliver the pipeline.
– Any prior examples of similar EC2 + Jenkins deployments you have completed.
– An estimated timeline for initial setup, testing, and final hand-off.
Looking forward to automating this deployment process together.
Here is what I need from you:
• A complete CI/CD pipeline that triggers on pushes to my Git repository, runs automated tests, builds an artifact, and pushes it to EC2 with zero-downtime or minimal-downtime deployment logic.
• Secure, repeatable AWS infrastructure for the pipeline itself—whether that is spun up through CloudFormation, Terraform, or another infrastructure-as-code approach you recommend.
• Parameterised Jenkins jobs (or a Jenkinsfile) with clear environment variables so I can promote the same build through dev, staging, and production.
• Automated rollback steps in case a deployment fails.
• Documentation I can hand to another engineer or use myself to modify the pipeline later.
The web application is already container-ready, but if you see a simpler path that still lands on EC2, I am open to suggestions. Other AWS native tools such as CodePipeline or Lambda can be mentioned in your proposal if they reduce maintenance, but Jenkins on EC2 is my baseline requirement.
Please include in your response:
– A brief outline of the steps you will take to deliver the pipeline.
– Any prior examples of similar EC2 + Jenkins deployments you have completed.
– An estimated timeline for initial setup, testing, and final hand-off.
Looking forward to automating this deployment process together.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.