CS

DevOps & Cloud Services

I get Drupal running on your own VPS or in the cloud — to the modern standards you already expect from development: everything in Docker, infrastructure described as code, deployments through CI/CD, and monitoring that speaks up on its own.

Deploying to a VPS or the cloud

Based on traffic and budget I pick what makes sense: a virtual server or AWS. I build the environment in Docker, so it is reproducible and identical in development and production. I prepare it alongside your current setup and switch over once it is verified — with no downtime.

Hosting and maintenance

I look after the site after launch too. On an ongoing basis that covers:

  • Security updates for Drupal and its modules
  • Uptime monitoring and alerts when something goes down
  • Backups, including regular verification that they actually restore
  • Deployments through CI/CD
  • Incident response

We size the scope to the site. I track my time and invoice the hours worked, so you pay exactly for what needed doing.

Infrastructure built to fit

  • Containerization: Docker images, Docker Compose, and container optimization
  • CI/CD pipelines: GitLab CI, GitHub Actions, automated testing and deployment
  • Cloud infrastructure: AWS (EC2, S3, RDS, Lambda)
  • Infrastructure as Code: Terraform and CloudFormation for reproducible infrastructure
  • Monitoring and logging: observability tooling (ELK stack)
  • Development environments: DDEV, so every developer works on the same configuration

Security

Security best practices, secrets and identity management, vulnerability scanning, and blue-green deployments so a change can be rolled back. Disaster recovery planning, including testing that it actually works.

Technologies & tools

  • Containers: Docker, Docker Compose
  • CI/CD: GitLab CI, GitHub Actions
  • IaC: Terraform, CloudFormation
  • Cloud: AWS
  • VPS: Linux, Docker

What you get

  • A site on infrastructure you control
  • One-click deployments with no manual steps
  • Backups you know actually work
  • An environment that can be rebuilt from source at any time

Frequently Asked Questions

Can the site be moved without downtime?
Yes. I prepare the environment in parallel, verify everything works, and switch DNS. Downtime is a matter of minutes.

Do we need our own server, or is cloud enough?
It depends on traffic and budget. Smaller sites are usually fine on a VPS; larger or spiky workloads justify AWS. I will recommend one once I know your numbers.

What if we end the engagement?
The infrastructure is described as code and runs on your accounts. I hand over documentation and access — nothing is locked in with me.

I run Drupal on your infrastructure so the site does not wake you up at night. Contact me on LinkedIn or use the form below.