Does Vedran only advise, or does he implement?

Vedran is hands-on. He inspects, explains, fixes, stabilizes, and documents the change path when access and scope allow.

What access is usually needed?

Usually temporary access to AWS, servers, Cloudflare or DNS, logs, and monitoring. Read-only access can be a good starting point for diagnosis.

AWS/Linux Production Troubleshooting

When production is slow, unstable, overloaded, or misconfigured

I help ecommerce, SaaS, WordPress, Magento/OpenMage, Shopify, and high-traffic platforms diagnose and stabilize AWS/Linux infrastructure when the problem crosses cloud, server, DNS, SSL, database, Cloudflare, and application behavior.

Get production help View Upwork proof

Common Problems I Fix

AWS is unclear or misconfigured

EC2, VPC, RDS, CloudFront, security groups, load balancers, VPN, Docker, ECS/EKS, and cost/performance issues need one coherent diagnosis.

Linux servers are overloaded

NGINX, Apache, PHP-FPM, MySQL, disk, CPU, memory, worker limits, cache layers, SSL, logs, and monitoring are inspected together.

Migrations feel risky

DNS, SSL, email records, app dependencies, origin exposure, and rollback paths are checked before production changes are made.

What I Inspect

AWS architecture: EC2, VPC, RDS, CloudFront, load balancers, security groups, VPN, ECS/EKS, Docker
Linux and web stack: NGINX, Apache, PHP-FPM, MySQL/Percona, Redis, Varnish, HAProxy, SSL, DNS, cron, logs
Production symptoms: downtime, slow TTFB, 5xx errors, worker saturation, resource spikes, regional DNS issues, failed deploys
Risk controls: backup state, access scope, rollback path, monitoring, staging/production differences, business-critical URLs

Proof Signals

This page is not a generic DevOps pitch. The public proof is Upwork-heavy: Top Rated Plus, 100% Job Success, 278 jobs, and 11,700+ hours across AWS, Linux, NGINX, Cloudflare, migrations, performance, hardening, and production troubleshooting.

TopRated Plus

100%Job Success

278Jobs

11.7K+Hours

FAQ

When should I bring you in?

When production is slow, unstable, down, expensive, risky to migrate, or blocked by conflicting explanations from hosts, developers, security tools, or cloud providers.

Do you only advise, or do you implement?

I am hands-on. I inspect, explain, fix, stabilize, and document the change path when access and scope allow.

What access do you need?

Usually temporary access to AWS, servers, Cloudflare/DNS, logs, and monitoring. Read-only access can be a good starting point for diagnosis.