Training course · Agentic Coding · DevOps & Cloud
Agentic Coding for DevOps and Cloud Teams
Use autonomous coding agents effectively: specs instead of prompts, task decomposition, test-driven loops, multi-agent setups and governance.
- Duration
- 2 days (14 hrs)
- Format
- Online or on-site
- Language
- German or English
- Participants
- open dates or exclusive for your team
- Certificate
- Certificate of attendance
Overview
“Agentic Coding for DevOps and Cloud Teams” is a hands-on course for roles such as DevOps engineers and platform teams, Cloud architects working with AWS, Azure or Google Cloud and Site reliability engineers responsible for operations and incidents. Rather than learning Agentic Coding in the abstract, you work on tasks from your daily routine – with examples, exercises and templates from DevOps & Cloud.
Agentic coding means working with AI agents that carry out development tasks largely on their own: they read code, plan changes, run commands and tests, and correct themselves based on the results. Tools such as Claude Code, OpenAI Codex, the GitHub Copilot coding agent and Cursor’s agent mode have made this way of working practical for everyday use. This vendor-neutral course teaches the underlying methodology so that you achieve reliable results whatever the tool, and redefine the developer’s role within your engineering team.
The core shift is from ad hoc prompts to robust specifications. You will learn to decompose and describe tasks so that agents solve them reliably, to set up test-driven loops in which tests act as objective acceptance criteria, and to run several agents in parallel or with a division of labour. We also cover review strategies for agent-generated code and team governance: permissions, security boundaries, accountability, cost control and the gradual introduction of agentic workflows into your existing development processes.
DevOps and cloud teams own infrastructure as code, CI/CD pipelines, monitoring, cost control and security – often across several cloud providers and on-premises environments. Much of the work is configuration in HCL, YAML and shell, troubleshooting through logs and cross-checking documentation. AI coding assistants and agents speed up exactly that: they write reusable Terraform modules, fix failing pipelines, create Ansible roles, analyse incident logs and propose cost optimisations. At the same time the stakes are high, because a single wrong command can hit production. This course teaches you to use agents productively with clear permission boundaries, plan-and-review workflows and safeguarded environments.
The course is delivered live – either online in a virtual classroom or on-site in our training rooms in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart and Kaiserslautern. We can also run it exclusively for your team.
Who is this course for?
- DevOps engineers and platform teams
- Cloud architects working with AWS, Azure or Google Cloud
- Site reliability engineers responsible for operations and incidents
- System administrators moving towards infrastructure as code
- Developers who maintain their own CI/CD pipelines
Typical challenges we address
- Growing volumes of Terraform, YAML and pipeline configuration with drift and duplication
- Time-consuming troubleshooting of failing pipelines and distributed logs
- Rising cloud costs without clear visibility
- High demands on security, compliance and traceability of changes
What you will be able to do
- You understand how coding agents work and choose the right tool and level of autonomy.
- You write specifications and project context that agents can work with reliably.
- You break initiatives into verifiable sub-tasks and steer agents through test-driven loops.
- You use multi-agent setups and parallel work in a controlled way.
- Use AI agents safely for infrastructure as code, pipelines and configuration management.
- Analyse incidents, pipeline failures and cloud costs faster with AI support.
- Define permission boundaries and approval processes so agents cannot make uncontrolled changes to production.
Course outline
Day 1
Module 1 Foundations of agentic development
- How coding agents work: tool calls, context windows and feedback loops
- Comparing tools: terminal agents, IDE agents and cloud agents
- Recognising suitable tasks and choosing levels of autonomy deliberately
- The new role in the team: from implementation to steering and acceptance
Module 2 Specifications instead of prompts
- Describing tasks with goal, context, constraints and acceptance criteria
- Keeping project context in files such as CLAUDE.md, AGENTS.md or rules
- Plan-first approach: let the agent draft a solution and review it before implementation
- Versioning specifications and maintaining them as part of the repository
Module 3 Task decomposition and test-driven agent loops
- Breaking large initiatives into independent, verifiable sub-tasks
- Having tests written first and using them as an objective stopping criterion
- Using linters, type checks and builds as automatic feedback
- Recognising stuck loops and restarting with a new strategy
Module 4 Multi-agent setups and parallel work
- Defining specialised subagents for research, implementation, testing and review
- Organising parallel work with branches, worktrees and isolated environments
- Orchestration: merging results and resolving conflicts
- Sharing tools and data sources through MCP
Day 2
Module 5 Review, security and team governance
- Review strategies for large, agent-generated changes
- Defining permissions, sandboxing and protection against prompt injection
- Embedding agents in CI pipelines and pull request processes
- Planning team guidelines, accountability, costs and a phased rollout
Module 6 Practice lab: DevOps & Cloud
- Developing Terraform modules
- Fixing CI/CD pipelines
- Ansible and configuration management
- Incident analysis
- Optimising cloud costs
- Policy as code and hardening
Module 7 Data protection, quality & transfer to daily work
- Agents with access to cloud accounts and pipelines are a security matter: work with least privilege, separate environments and human approval, and keep cloud credentials, state files and secrets out of prompts. Operators of essential and important services must also meet NIS2 requirements on risk management, supply-chain security and traceability of changes.
- Ground rules for safe AI use in your team
- Checking results: facts, sources, tests and the four-eyes principle
- Personal action plan for the next 30 days
- Open questions, outlook and resources for further learning
Practical scenarios from your field
Developing Terraform modules
The agent creates reusable Terraform or OpenTofu modules with variables, validations and outputs, runs fmt, validate and plan, and explains every planned change before a human approves the apply.
Fixing CI/CD pipelines
Failed GitHub Actions, GitLab CI or Azure DevOps runs are analysed from their logs, root causes such as caching issues or missing permissions identified and corrected pipeline definitions proposed.
Ansible and configuration management
The AI writes idempotent Ansible roles, templates and inventories, replaces fragile shell scripts and adds Molecule tests so configuration stays reproducible. Existing roles are gradually standardised along the way.
Incident analysis
Logs, metrics and alerts from monitoring are brought together, a timeline reconstructed, likely causes narrowed down and a draft postmortem with actions produced. The team keeps the final judgement.
Optimising cloud costs
The assistant reviews cost reports and resource definitions, finds oversized instances, orphaned volumes or missing lifecycle rules and drafts the matching IaC changes. Each recommendation includes estimated savings.
Policy as code and hardening
IaC code is scanned with tools such as Checkov or tfsec, findings are fixed and rules for encryption, tagging or network access are expressed as policy as code.
Possible hands-on projects
Drift detector
A script that regularly runs terraform plan across several environments, detects drift and posts a summary to a chat channel.
Pipeline template library
Reusable CI/CD templates for build, test, security scanning and deployment, documented and accompanied by sample projects. Teams adopt them with just a few lines of configuration.
Cost report tool
A CLI that pulls cost data from a cloud account, breaks it down by tags and teams and clearly highlights optimisation candidates.
Prerequisites
You have several years of development experience, are confident with Git, testing and CI, and ideally have already used AI coding tools. Practical experience with Linux, Git and at least one cloud platform, plus a working knowledge of Terraform, containers and CI/CD.
Technical requirements
Your own laptop with Git, a terminal and your development environment, plus access to at least one coding agent such as Claude Code, Codex, Copilot or Cursor.
Data protection & compliance
Agents with access to cloud accounts and pipelines are a security matter: work with least privilege, separate environments and human approval, and keep cloud credentials, state files and secrets out of prompts. Operators of essential and important services must also meet NIS2 requirements on risk management, supply-chain security and traceability of changes.
Suggested dates
All dates are suggestions – your preferred date is always possible.
- Wed, 25 November 2026 – Thu, 26 November 2026 Online Request
- Wed, 9 December 2026 – Thu, 10 December 2026 Salzburg Request
- Mon, 14 December 2026 – Tue, 15 December 2026 Online Request
- Thu, 14 January 2027 – Fri, 15 January 2027 Bremen Request
- Thu, 21 January 2027 – Fri, 22 January 2027 Online Request
- Mon, 1 February 2027 – Tue, 2 February 2027 Augsburg Request
Frequently asked questions
How does agentic coding differ from vibe coding?
Vibe coding relies on fast, intuitive iteration in natural language and is particularly suited to prototypes. Agentic coding is an engineering discipline for professional codebases: precise specifications, tests as acceptance criteria, clear permissions and structured reviews ensure that agents deliver reliable, maintainable results even in complex, long-lived projects.
Is the course tied to a specific tool?
No. The course teaches methods that work with Claude Code, OpenAI Codex, the GitHub Copilot coding agent, Cursor and comparable tools. The exercises highlight differences and common ground, for example in context files, permissions and subagents. You can work with whichever tool your organisation already uses or plans to adopt.
How do we stay in control of quality and security with autonomous agents?
Control comes from several layers: tightly scoped permissions and sandboxing, tests and static analysis as automatic checks, mandatory human review before merging, and clear team rules on accountability. During the course you develop a governance concept that fits your processes, security requirements and regulatory obligations.
Should an AI agent be allowed to apply infrastructure changes itself?
That is something to limit deliberately. A proven workflow has the agent write code and run plan, a human review the result and the apply run through the regular pipeline. On the course you learn to design permissions, sandbox environments and approvals so that production systems stay protected.
Which cloud platform does the course use?
The methods are vendor-neutral and transfer to AWS, Azure and Google Cloud. Exercises use examples you can reproduce with local tooling or test accounts. You are welcome to bring scenarios from your own platform, provided no production credentials are used.
How much does “Agentic Coding for DevOps and Cloud Teams” cost?
The course costs a flat €949 plus VAT per participant – whether online or on-site. This includes 2 training day(s) with a live trainer, course materials, a lab environment and a certificate of attendance.
Can I suggest my own date?
Yes. Our suggested dates are just a guide. In the request form you can always describe your preferred date or period in free text – we check availability and confirm within one working day.
Is the course online or on-site?
Both are possible: live online in a virtual classroom or on-site in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart or Kaiserslautern. We can also run the course exclusively for your team.
More courses for DevOps and Cloud Teams
- Claude Code for DevOps and Cloud Teams
- Vibe Coding for DevOps and Cloud Teams
- Cursor for DevOps and Cloud Teams
- GitHub Copilot for DevOps and Cloud Teams
- OpenAI Codex for DevOps and Cloud Teams
- Windsurf for DevOps and Cloud Teams
- Model Context Protocol (MCP) for DevOps and Cloud Teams
- AI Agent Development for DevOps and Cloud Teams
- RAG & LLM Applications for DevOps and Cloud Teams
More Agentic Coding courses
- Agentic Coding for Internal Tools and Automation
- Agentic Coding for Java and Spring Developers
- Agentic Coding for JavaScript and TypeScript Developers
- Agentic Coding for Kubernetes and Microservices Teams
- Agentic Coding for Legacy Modernisation
- Agentic Coding for Startups and MVP Development
- Agentic Coding for Mobile Developers
- Agentic Coding for Node.js Back-End Developers
- Agentic Coding for PHP Developers
- Agentic Coding for Python Developers
- Agentic Coding for React and Front-End Developers
- Agentic Coding for Rust Developers
Agentic Coding · MunichAgentic Coding · SalzburgAgentic Coding · BerlinAgentic Coding · AugsburgAgentic Coding · HanoverAgentic Coding · BremenAgentic Coding · StuttgartAgentic Coding · KaiserslauternAgentic Coding · Online