I will setup github actions or gitlab ci cd pipeline for automated deployment
DevOps Engineer
About this Gig
Still manually SSHing into servers to pull code, build images, and restart containers on every release?
Manual deployments waste developer hours and risk costly downtime from unverified commits. I am an AWS Certified DevOps engineer specializing in designing automated, fail-safe CI/CD workflows using GitHub Actions and GitLab CI/CD. I build pipelines that test, build, and deploy your code reliably on every push.
What I Build & Automate:
- CI Test & Quality Gates: Automated linting, unit/integration testing, and dependency audits on every Pull Request.
- Container Automation: Multi-stage Docker image builds with aggressive layer caching, pushed securely to Docker Hub, AWS ECR, or GitHub Packages.
- Zero-Downtime CD: Automated deployment triggers to AWS EC2, ECS Fargate, DigitalOcean, or private VPS via secure SSH/runners.
- Environment Separation: Isolated pipelines for Staging and Production with branch protection rules and secret management.
Why Work With Me?
- AWS Certified: Built to enterprise security standards.
- Secret Protection: Zero plain-text credentials or API leaks.
- Clean & Documented: Well-commented .yml files.
Message me your tech stack before ordering!
Tools:
Docker
•
GitLab
•
GitHub
Frameworks:
Npm
•
Terraform
Cloud Provider:
Amazon Web Services
Programming language:
Bash
•
JavaScript
•
Python
•
PowerShell
Expertise:
Migration
•
Debugging
•
Configuration
My Portfolio
Other DevOps Engineering Services I Offer
FAQ
How do you handle sensitive credentials and production secrets securely?
I follow strict security and least-privilege standards. No passwords, private keys, or API tokens are ever hardcoded in pipeline YAML files. All sensitive values are stored securely using GitHub Secrets or GitLab CI/CD Masked Variables, or fetched dynamically via AWS IAM OpenID Connect (OIDC) to eli
Can you build deployment pipelines for private servers or VPS providers other than AWS?
Yes. I create automated workflows that deploy directly to AWS (EC2, ECS, S3/CloudFront), DigitalOcean droplets, Hetzner, Linode, or any private dedicated Linux server using secure SSH deployment keys, self-hosted runners, or webhook triggers.
Do you support monorepo setups or multi-service microservice architectures?
Yes. I configure change-path filters (path-based triggering) so workflows execute only when specific microservice directories change. This avoids running redundant builds across unaffected services, significantly reducing pipeline run times and CI minutes usage.
Will you provide documentation on how to modify or maintain the pipeline?
Yes. All .github/workflows or .gitlab-ci.yml files are written with clear inline comments explaining each build stage, environment variable, and trigger. You will receive an operational overview so your development team can easily update steps or add future deployment targets.

