AWS DevOps Pipeline Setup
Budget / Salary$10–30
TypeFreelance project
LocationRemote
Posted2 hours ago
I’m looking to bring a seasoned DevOps mind on board to tighten up our AWS workflow. The immediate focus is three-fold:
1. Turn our manual deployments into a clean CI/CD stream. We already run Jenkins, so I need multi-stage pipelines built and wired to our repos, complete with automated testing and blue-green or canary releases where it makes sense.
2. Express the entire stack in Terraform. Every VPC, subnet, security group, EKS cluster, and supporting service should be reproducible from code and kept in version control so we can spin up identical environments on demand.
3. Add robust monitoring and logging. Think CloudWatch metrics and logs, sensible alarms, dashboards, and log retention policies that let the team trace issues quickly without drowning in noise.
You’ll be working inside AWS exclusively; alternatives like Azure or GCP aren’t on the table for this project. If you can demonstrate previous Jenkins + Terraform success stories and clearly outline how you’ll measure a successful rollout, let’s talk.
Deliverables I expect:
• Production-ready Jenkins pipeline definitions checked into Git
• Terraform modules and state setup, with a README covering bootstrap and destroy commands
• Monitoring dashboards and alert rules active in our AWS account
• A brief hand-off session (recorded) walking through the new workflow and IaC repository structure
Everything should land in our existing GitHub org, pass code review, and deploy end-to-end without manual tweaks. Looking forward to your approach.
1. Turn our manual deployments into a clean CI/CD stream. We already run Jenkins, so I need multi-stage pipelines built and wired to our repos, complete with automated testing and blue-green or canary releases where it makes sense.
2. Express the entire stack in Terraform. Every VPC, subnet, security group, EKS cluster, and supporting service should be reproducible from code and kept in version control so we can spin up identical environments on demand.
3. Add robust monitoring and logging. Think CloudWatch metrics and logs, sensible alarms, dashboards, and log retention policies that let the team trace issues quickly without drowning in noise.
You’ll be working inside AWS exclusively; alternatives like Azure or GCP aren’t on the table for this project. If you can demonstrate previous Jenkins + Terraform success stories and clearly outline how you’ll measure a successful rollout, let’s talk.
Deliverables I expect:
• Production-ready Jenkins pipeline definitions checked into Git
• Terraform modules and state setup, with a README covering bootstrap and destroy commands
• Monitoring dashboards and alert rules active in our AWS account
• A brief hand-off session (recorded) walking through the new workflow and IaC repository structure
Everything should land in our existing GitHub org, pass code review, and deploy end-to-end without manual tweaks. Looking forward to your approach.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.