I’m Todor Shopov, a Senior Cloud / DevOps / Platform Engineer. I design, migrate, and operate cloud-native systems—Kubernetes, infrastructure as code, GitOps, security, and production operations—on AWS and Azure.
A Deployment replaces pods. Only Ready pods receive traffic.
Operate Healthy baseline. Illustrative GitOps model using Flux CD.
Primary expertise is the daily architectural and operational practice. Hands-on experience is work delivered and operated. Familiarity is working knowledge without a production specialty claim.
Account structure, identity, networking, and managed services for production environments on AWS and Azure.
Primary expertise
Familiarity
Managed Kubernetes operating models, image delivery, and workload identity rather than cluster novelty.
Primary expertise
Hands-on experience
Reviewable, modular infrastructure with environment promotion instead of Console-built snowflakes.
Primary expertise
Hands-on experience
Build, scan, sign, and promote artifacts; reconcile desired state; roll back without rebuilding history.
Primary expertise
Hands-on experience
Private connectivity, DNS, load balancing, and service entry so workloads are reachable by design, not by exception.
Primary expertise
Hands-on experience
Familiarity
Least privilege, secret handling, and supply-chain checks in the delivery path rather than a later audit.
Primary expertise
Hands-on experience
Metrics, logs, and traces that explain user impact, with alerts that have owners and a next step.
Primary expertise
Hands-on experience
Managed stores and queues as platform dependencies: backup, identity, network path, and failure domains.
Primary expertise
Hands-on experience
Linux, Git, registries, and the operating habits that keep a platform consistent as teams grow.
Primary expertise
Hands-on experience
Explore how cloud-native applications move from a reviewed change to a verified, observable service.
Route traffic to ready replicas and validate application behavior in the target environment.
Challenge: A running container is not necessarily a working service.
Practice: Verify dependencies and use application-level smoke tests.
Read the technical guideWaiting for a simulated deployment…
No cloud resources will be created.
Ready to run.
Cloud architecture, Kubernetes, delivery automation, security, observability, and cost—connected disciplines, not a résumé list.
Designing secure, scalable, and cost-conscious cloud environments built for reliability, automation, and long-term growth.
Explore expertiseTurning complex delivery processes into reliable, repeatable workflows through automated pipelines and modern engineering practices.
Explore expertiseBuilding internal platforms that simplify development, standardize environments, and make the path from code to production faster and safer.
Explore expertiseIntegrating security into infrastructure and delivery workflows through strong access controls, secure configurations, and automated checks.
Explore expertiseCreating observable systems with actionable telemetry, meaningful alerts, and operational practices that support resilient services.
Explore expertiseImproving cloud efficiency through resource analysis, right-sizing, architecture reviews, and cost-aware infrastructure decisions.
Explore expertiseProviding practical technical guidance, infrastructure assessments, architecture recommendations, and hands-on engineering support.
Explore expertiseEducational examples of how the disciplines connect. They are not client projects, case studies, or measured results.
Educational reference
Educational layout for isolated accounts, private EKS workloads, and GitOps promotion. Not a client topology.
Educational reference
Educational private-cluster pattern: VNet isolation, private API, Key Vault, and private endpoints. A teaching counterpart to the AWS network figure.
Educational reference
Educational delivery path: one digest, scan policy, Flux reconciliation, and rollback as Git plus cluster health.
Understand readiness, surge capacity, graceful shutdown, and telemetry without treating rolling updates as an availability guarantee.
Network boundaries, state isolation, reviewed changes, and recovery planning for a hypothetical AWS workload.
Build once, use short-lived identities, protect release gates, and verify the artifact you actually deploy.