Cloud, DevOps & DevSecOps — fundamentals

Objectives

• Design the cloud architecture of a given application (network, compute, storage, database, backups) and estimate its monthly cost
• Containerise an application and deploy it to a cloud environment
• Build a continuous integration and deployment pipeline that includes automated tests, dependency analysis and secret detection before any release to production
• Set up monitoring (logs, metrics, alerts) and a backup whose restoration has been tested
• Apply the basic DevSecOps rules: least-privilege identities and access, secrets kept out of the code, logging of administration actions

Audience

System administrators, developers, IT managers, IT teams taking over an application or an infrastructure built by a provider.

Prerequisites

Be able to administer a Linux server from the command line and know the basics of networking (IP address, DNS, ports). Checked by a placement test.

Technical prerequisites

• One laptop per participant with Docker, Git and a code editor installed before the first day (procedure supplied with the invitation).
• Training cloud accounts and credits supplied by Yolea.
• Training Git repository.
• For remote attendance, a stable connection of at least 10 Mbit/s, microphone and camera.
• Training application supplied; the participant's own application accepted if its code is available.

Skills covered

• Cloud architecture and cost control
• Containerisation
• Secure continuous integration and deployment
• Monitoring and backup
• Access and secrets security

Programme

• 30% input, 70% hands-on workshops.
• One application used throughout the course, taken from the local machine to monitored production.
• Tools of the current edition: Docker, GitHub Actions, Terraform as an introduction, monitoring through logs and metrics, cloud provider chosen to suit the client's constraint.
• Practical cases inspired by company situations (putting an agent into production, mixed hosting with sensitive data kept at the client's site, recovery after an incident).
• Materials supplied: reference repository, pipeline templates, DevSecOps checklist, cost estimation grid, glossary.
• Personal action plan.
• Follow-up session after three weeks.

Format

21 hours, 3 consecutive days of 7 hours, or 2 + 1 days a week apart. In person recommended, hybrid possible; in-company or open enrolment; 8 to 12 participants.

Assessment

Beforehand, a placement test. During the course, check quizzes and a practical challenge (deploy a set application with a pipeline, monitoring and a tested backup, assessed against a grid). At the end, an immediate feedback evaluation and a named certificate of completion. After three weeks, a follow-up session.

The last exercise is an action plan: three real tasks that you leave ready to equip with tools.