An AI assistant adds a firewall rule for a new service to the infrastructure code. In review the change looks harmless, yet after deployment the port is reachable from the whole internet instead of the internal network only. So you practise both sides here: using AI for infrastructure as code, in CI/CD pipelines and in incidents, and setting up the controls around those changes, from automated policy checks to minimum permissions for agents.
Once AI changes code or infrastructure in your pipeline, someone must set its limits. In tecnovy's AI for DevOps Engineers, DevOps, platform and site reliability engineers set permissions, checks and logs, and use AI up to incident analysis.
How the training runs
Method
Hands-on in an example environment with pipeline, containers and monitoring
Basis
tecnovy curriculum for AI along the DevOps chain
Outcome
tecnovy certificate of participation, no examination
Dates & booking
Choose a date that fits
No public dates are scheduled yet.
New dates are published regularly. Join the waitlist or plan an in-house course for your team.
You write and maintain infrastructure code and container configuration for your services.
You look after CI/CD pipelines and the cloud infrastructure they run on.
You handle incidents and operations tasks and want to use AI for them deliberately.
Prerequisites
No prerequisites
You can start right away. What you need: experience with CI/CD, experience with containers, experience with infrastructure as code.
Consider insteadLLMOpsIf your team operates AI applications itself: you version prompts and models, make evaluation the release gate, and set alerts and budgets.
Curriculum
AI for DevOps Engineers in Detail
From planning to monitoring the course follows the DevOps chain, practised in an example environment with pipeline, containers and monitoring: you place the uses of AI, apply it to infrastructure code, in the pipeline and in operations, and finally set permissions, secrets and the traceability of automated changes.
01AI in the DevOps cycle
You place where AI can work along the DevOps chain and where changes become risky.
Uses from plan through build and deploy to monitor
Where an AI suggestion acts directly on infrastructure and operations
Risks of automated changes to infrastructure
02Infrastructure as code with AI
AI generates and explains configuration, and automated checks test it before it is used.
Generating configurations with AI
Having existing configuration explained and checking it
Policy checks: rules every configuration passes automatically before deployment
Automating security checks
03AI in CI/CD
Reviews, tests and troubleshooting get AI support, and you decide what AI may do in the pipeline.
AI reviews of changes
Test generation with AI
Diagnosing failed pipeline runs
Coding agents in the pipeline: which permissions they get and what they may touch
04Operations and incidents
During an incident AI evaluates data and drafts texts that you check before acting on them.
Analysing logs and metrics with AI
Runbooks: step-by-step guides for recurring operations tasks
Postmortems: the review after an incident
Incident communication
05Security and governance
The principle of minimum permissions is applied here to AI along the DevOps chain.
Minimum permissions for agents
Managing secrets: credentials such as passwords, tokens and keys
Traceability: who or what triggered an automated change
Outcome
What you will be able to do afterwards
01
You map uses of AI to the stages of the DevOps chain from plan to monitor and name the risks of automated infrastructure changes.
02
You have AI generate or explain infrastructure configuration and check it before it is used.
03
You automate policy and security checks, meaning rules every configuration has to pass before deployment.
04
You use AI in the CI/CD pipeline for reviews, test generation and diagnosing failed runs.
05
You decide which permissions coding agents, AI tools that change code and run commands on their own, get in a pipeline.
06
You analyse an incident's logs and metrics with AI and check the results against the data.
07
You use AI to draft runbooks, step-by-step guides for operations tasks, as well as postmortems and incident communication.
08
You set how agents obtain secrets such as tokens and keys, and log who or what triggered an automated change.
tecnovy Teilnahmezertifikat
Confirms your attendance and the curriculum covered in the training. Issued by tecnovy, shareable on LinkedIn.
Prompt templates and example pipelines for DevOps tasksYou receive the templates and pipelines from the exercises, for example for configuration, pipeline diagnosis and postmortems.
AI for DevOps
Why tecnovy
What you get on top with us
01
No Slideshow, Hands-On!
Promised: no PowerPoint marathon. We work in groups, tie theory to practice, and you get real project examples from our experienced trainers plus the exchange with like-minded people.
02
Certificate Showroom
Get your certificate of participation and, if you have one, add your exam certificate from E-Learning. Fully automated, beautifully designed. Just for you, only at tecnovy.
03
Flexible Date Change
If you are not able to attend the course, you can rebook your training free of charge up to one week before the start of the training.
04
Attend Twice, Pay Once
You are welcome to attend the training online again within a year as a refresher.
05
Learn from Experts
We always guarantee you the use of didactically and methodically first-class qualified trainers who draw their knowledge from training experience as well as professional practical and project experience.
FAQs
Frequently asked questions
01Is AI for DevOps Engineers an AIOps course?
Partly. AIOps means AI in IT operations, such as evaluating monitoring data, alerts and incidents, and the tecnovy AI for DevOps Engineers training covers that part. It also covers AI for infrastructure as code and in CI/CD pipelines.
02Which platforms does the training use?
The tecnovy AI for DevOps Engineers training works with a widely used CI/CD platform and a container environment and is tied to no vendor. The exercises also need access to an AI tool that can work on code and configuration.
03May code, logs and secrets go to an AI tool?
Your company decides that, based on its policies and the provider's terms. In the tecnovy AI for DevOps Engineers training you set the permissions agents work with and how secrets are managed; no setting rules out every risk.
04May an AI agent push changes to production on its own?
Your team decides that, not the tool. In the tecnovy AI for DevOps Engineers training you set which permissions an agent gets in the pipeline, which changes it may only propose, and how every automated change is logged.
05Does AI resolve incidents faster?
Not by itself: an AI tool can misread logs and name causes that are wrong. In the tecnovy AI for DevOps Engineers training you practise checking an AI analysis against logs and metrics before you act on it.
06How does this differ from AI for Developers?
The tecnovy AI for Developers training starts from development work: comparing tools, checking code, adding an LLM function. AI for DevOps Engineers starts from infrastructure, pipelines and operations, and from which permissions AI gets there.
07How does AI for DevOps Engineers differ from LLMOps?
AI for DevOps Engineers uses AI in your DevOps work. The tecnovy LLMOps training starts from a different place: there you operate AI applications yourself, with versioned prompts and models, evaluation as the release gate, rollouts, alerts and budgets.
08Does the training end with an examination?
No, AI for DevOps Engineers is a tecnovy course with no examination and no certification. With at least 80% attendance you receive the tecnovy certificate of participation.
What does your training at tecnovy look like?
AI for DevOpsAI for DevOps Engineers
No dates yet
We will let you know as soon as the next date is scheduled.