Kategorien durchsuchen
Entdecken
Fiverr Pro
Deutsch
$
USD
I will set up your cicd pipeline with jenkins, gitlab, github actions or AWS
DevOps Engineer, AWS Cloud Engineer
Senior AWS and DevOps Engineer with 5 years of production experience, running 10+ client production AWS accounts at a managed services provider. 10 certifications, including AWS Solutions Architect Pr...
Über diesen Service
Your code should be built, tested, and live minutes after a push. I build CI/CD pipelines that do exactly that, in the tool you already use.
Jenkins, GitLab CI, Bitbucket Pipelines, GitHub Actions, AWS CodePipeline, Azure DevOps, CircleCI, or GitOps delivery with Argo CD: pick one, or tell me your stack and I will recommend the right fit. The stages, gates, and security standards stay the same, whichever tool runs them.
Every package is a working pipeline verified with real runs: build, test, scan, package, and deploy to ECS, EKS, or Kubernetes, Lambda, S3 + CloudFront, EC2, or VMs, with short-lived credentials and no static keys.
What you get:
- Pipeline definitions committed to your repo in your tool's native format
- Docker and dependency caching for fast runs
- Approval gates before production
- Health checks with a rollback path, Slack or Teams notifications
- README and runbook so your team owns it
Why me: AWS DevOps Engineer Professional, AWS Solutions Architect Professional, CKA and CKAD, 10 certifications, 5 years running production delivery pipelines across 10+ client accounts.
Message me with your repo, tool, and target, and I will confirm the right package.
Tools:
Docker
•
GitLab
•
Jenkins
•
GitHub
•
CircleCI
Frameworks:
Npm
•
Terraform
•
Ansible
•
Koch
•
Puppe
Cloud-Provider:
Amazon Web Services
Expertise:
Installation
•
Entwicklung
•
Konfiguration
Meine weiteren Dienstleistungen im Bereich DevOps-Engineering
FAQ
Which CI/CD tool should I choose?
If you already have one, we use it: Jenkins, GitLab CI, Bitbucket Pipelines, GitHub Actions, CodePipeline, Azure DevOps or CircleCI. If not, I recommend based on where your code lives and where it deploys. For Kubernetes targets I usually add Argo CD for GitOps delivery.
Do you need access to my repo and cloud account?
I need a collaborator invite to the repository and an IAM role or service connection scoped to the deployment, which you remove when the work is done. No root credentials, and no long-lived access keys stored in the CI tool: pipelines use OIDC or managed identities wherever the tool supports it.
Can you migrate my pipeline from one tool to another?
Yes. Common moves are Jenkins to GitLab CI or GitHub Actions, Bitbucket to GitHub, and CodePipeline to a Git-native tool. I rebuild the stages in the new tool, keep both running until parity is verified, then cut over. Migration is included in Premium and available as an extra otherwise.
Which languages, frameworks and targets do you support?
Node, Python, Go, Java, .NET, PHP and static frontends; Docker-based projects work with any language. Targets: ECS, EKS or any Kubernetes, Lambda, S3 with CloudFront, EC2 or VMs, Elastic Beanstalk. If the infrastructure does not exist yet, pair this with my Terraform gig.
Do I own the pipeline, and can my team maintain it?
Everything is pipeline-as-code committed to your repository, with a README and runbook. I hold 10 certifications including AWS DevOps Engineer Professional, AWS Solutions Architect Professional, CKA and CKAD, so the pipeline follows current practice your team can build on.
