6 дней назад

DevOps Engineer

  • Удалённо
  • Полная занятость
DockerCI/CDLinuxAWSDevSecOpsAnsibleSecurityVPNNginxWireGuard

Описание

Responsibilities

  • Server and VPS
  • - Select and purchase servers/VPS for tasks.
  • - Choose a provider and configuration.
  • - Commission servers: OS, disks, network, access.
  • - Set up monitoring and basic status control.
  • - Maintain the infrastructure in working order.
  • Docker
  • - Build and maintain production environments.
  • - Work with Docker images, networks, and volumes.
  • - Configure deployment and rollback.
  • - Organize log storage and viewing.
  • - Ensure that containers are isolated and do not create unnecessary risks.
  • WireGuard / VPN
  • - Set up and maintain WireGuard.
  • - Configure team access to infrastructure.
  • - Work with keys and their rotation.
  • - Configure routing and segmentation.
  • - Implement the principle of "access only where absolutely necessary."
  • AWS
  • - Work with AWS without excessive "cloud magic":
  • - VPC
  • - EC2
  • - IAM
  • - S3
  • - Security Groups
  • - Backups
  • - Cost control and optimization
  • Security & Hardening
  • - Configure secure SSH access.
  • - Use keys instead of passwords.
  • - Configure firewall.
  • - Keep packages and OS up to date.
  • - Work with fail2ban or its analogs.
  • - Minimize privileges and the number of open ports.
  • - Securely store and use secrets.
  • - Perform basic infrastructure audit.
  • - The main principle: no 0.0.0.0/0 just because it's faster.
  • Network and production
  • - TLS / SSL.
  • - DNS.
  • - Reverse proxy.
  • - Separation of public and administrative circuits.
  • - Backups.
  • - Understanding the process of recovery after a failure.
  • - Prod should not just work - it should be clear what to do if it stops working at 3 AM.
  • Documentation
  • - Document the infrastructure:
  • - - what is running where;
  • - - which servers are responsible for what;
  • - - who has access to where;
  • - - how the network is set up;
  • - - how to deploy;
  • - - how to roll back;
  • - - how to restore the system after a failure.

Requirements

  • Linux
  • - Production level:
  • - - systemd;
  • - - network;
  • - - disks and file systems;
  • - - users and permissions;
  • - - packages;
  • - - problem diagnostics.
  • Docker
  • - Not just docker compose up on a laptop, but real production operation.
  • WireGuard / VPN
  • - Understanding:
  • - - keys;
  • - - routes;
  • - - peers;
  • - - split access;
  • - - network segmentation.
  • AWS
  • - EC2;
  • - VPC / networking;
  • - IAM;
  • - S3.
  • - Terraform / CloudFormation - a big plus, but not a mandatory filter.
  • Understanding of basic server security:
  • - closed SSH;
  • - key-based authentication;
  • - minimum open ports;
  • - firewall;
  • - regular updates;
  • - principle of minimal privileges;
  • - basic audit.
  • - And most importantly - understanding why all this is needed, not just a set of commands from a guide.

Nice to have

  • Caddy / Nginx
  • CI/CD - GitHub Actions / GitLab CI
  • GHCR
  • Experience with multiple VPS
  • Separation of app / edge
  • Separate administrative circuit
  • PostgreSQL from an operational perspective:
  • - backups;
  • - access;
  • - recovery.
  • Understanding of typical attacks on:
  • - SSH;
  • - control panels;
  • - docker.sock.
  • Ansible or custom scripts for server configuration automation.

We offer

  • We are looking for a DevOps Engineer who is ready to take the infrastructure as a whole - from purchasing hardware and setting up VPS to hardening, VPN, and stable production deployment.
  • We need not a person in the format of "set up CI and forget", but an engineer who understands how servers, networks, security, and production work, and is ready to be responsible for the infrastructure systemically.
  • A person who is not afraid of production;
  • can independently figure out problems;
  • understands the consequences of their changes;
  • thinks about security in advance;
  • dislikes manual routine and automates it;
  • can explain to developers why something is insecure and offer a normal solution;
  • can look at the infrastructure as a whole, and not just at a separate Docker container.