← All servicesService

DevOps on AWS: CI/CD and infrastructure as code

Deploying stops depending on one person: automated pipelines and infrastructure declared in a repository.

Get a DevOps assessmentThe quote comes out of the assessment.

01When it makes sense

  • Only one person knows how to deploy.
  • If the server were lost, nobody could rebuild it.
  • Every new environment is set up by hand.

02How the work goes

  1. 01

    Assess

    How a change reaches production today, and where it gets stuck.

  2. 02

    Pilot

    One pipeline end to end, tested before production.

  3. 03

    Rollout

    To the other applications and environments.

  4. 04

    Handoff

    Documentation, runbooks and a session with your team.

03What is included

  • GitHub Actions, GitLab CI or AWS CodePipeline.
  • Terraform or CloudFormation.
  • Deployment on ECS, EKS or Lambda.
  • Automatic rollback, and manual approval for anything that deletes data.

What is not

  • Being your on-call after handoff.

04Records

Two infrastructures written entirely as code.

05Questions

Do I have to change tools?
No. If what you use works, it stays.
How much does it cost?
It comes out of the assessment: with the inventory I put together a quote, and you approve it before anything starts. What AWS bills is pay-per-use and goes straight to AWS.
Who owns what gets built?
You do: everything lives in your repositories.

Tell me what you have today and I will reply, almost always within 24 hours.

Get a DevOps assessment