DevOps Engineer focused on reliable delivery, infrastructure automation and observable production systems. I build reproducible environments, secure CI/CD pipelines and Kubernetes platforms using Infrastructure as Code.
| Area | Technologies |
|---|---|
| Cloud and infrastructure | AWS, EKS, VPC, IAM, Terraform |
| Containers | Docker, Docker Compose, Kubernetes, Helm |
| CI/CD and security | GitHub Actions, GitLab CI, Trivy, Semgrep, Checkov, Gitleaks |
| GitOps | Argo CD, immutable image tags, automated reconciliation |
| Observability | Prometheus, Grafana, Loki, Alertmanager |
| Automation and systems | Linux, Ansible, Bash, Nginx, Traefik |
| Reliability | Backups, restore drills, health checks, SLO/SLI, incident runbooks |
- AWS EKS GitOps Platform — Terraform-provisioned VPC and EKS with Helm and Argo CD.
- DevSecOps Pipeline — tests, SAST, secret scanning, IaC scanning and container vulnerability reports.
- Production Observability Platform — Prometheus, Alertmanager, Loki, Promtail and Grafana dashboards.
- Ansible Linux Hardening — SSH hardening, UFW, Fail2ban and automatic security updates.
- Disaster Recovery Lab — PostgreSQL backups, integrity checks, S3 copies and restore procedures.
Every project includes architecture documentation, reproducible commands, CI validation and a failure or recovery scenario.
- Infrastructure should be reproducible and reviewable.
- Deployments should be automated, observable and reversible.
- Security checks belong in CI, not only after an incident.
- Backups are only useful when restores are tested.
- Production claims should be supported by measurable evidence.
- English: Intermediate
- Ukrainian
- Russian