I will build your ci cd pipeline with github actions gitlab or jenkins
Cloud and DevOps Engineer, AWS and Kubernetes, Web and Mobile Apps
About this Gig
You get a pipeline that tests every change and deploys it the same way every time, in the CI tool you already use: GitHub Actions, GitLab CI or Jenkins.
Deploys to AWS use short-lived credentials (OIDC or an instance role) instead of long-lived access keys stored in the CI. Staging deploys on merge, production after an approval.
Targets I work with: ECS Fargate, Lambda, S3 with CloudFront, EC2 and EKS, plus Kubernetes with Argo CD. Docker builds are cached so pipelines stay fast.
In the Premium package the AWS side is written in Terraform, so it can be rebuilt or copied to a new environment, and you get a rollback to the previous version plus CloudWatch alarms.
I'm AWS DevOps Engineer Professional and Solutions Architect Professional certified and build CI/CD with GitHub Actions, GitLab CI, Jenkins and Argo CD for production teams. You get a short README so your team can run and change the pipeline without me.https://www.upwork.com/jobs/~022112991820914457572
Tools:
Docker
•
GitLab
•
Jenkins
•
GitHub
Frameworks:
Terraform
•
Ansible
Programming language:
Bash
•
JavaScript
•
Python
Expertise:
Debugging
•
Development
•
Configuration
My Portfolio
Other DevOps Engineering Services I Offer
FAQ
Why no stored access keys?
Keys stored in a CI tool can leak and never expire. Short-lived credentials only allow the deploy and expire after each run.
Will you change my application code?
Only build-related files, such as the Dockerfile or build scripts, and only after I tell you why.
What if my app is not on AWS yet?
Tell me where it runs today. Moving it to AWS can be part of the Standard or Premium package.
Which CI tool do you use?
The one you already have: GitHub Actions, GitLab CI or Jenkins. If you have none, I suggest the one that fits where your code lives.
