Automation with Claude
Certificate Renewal Automation with Claude
From expiring certificate to renewed, validated and audited binding on every load balancer.
0:00 / 0:00
- Instructor-led training: Online or Destination
- 3 days · 24 hours
- Starts in about 3 weeks
- Flexible and customizable
What you will be able to do
- Explain the certificate lifecycle as each load balancer platform implements it and where renewal outages really come from
- Set up Claude Code, the Claude Agent SDK and an MCP server as a safe workbench for certificate operations
- Build a typed certificate inventory from F5 iControl REST, NetScaler NITRO, Radware Alteon and other load balancers (Anaya LB)
- Use a Claude planning agent to draft renewal plans as structured JSON and open ServiceNow change records with citations to inventory evidence
- Write deterministic, pytest-covered executors that upload, install, bind and verify certificates per platform
- Enforce guardrails, human approval, pre- and post-checks, automatic rollback and an audit trail reviewable through GitHub pull requests and Actions
Table of contents
- 1Certificate lifecycle on load balancers and the automation baseline
- 2Setting up Claude Code, the Agent SDK and MCP for certificate work
- 3Certificate inventory and expiry discovery across platforms
- 4Renewal planning agent and ServiceNow change records
- 5Deterministic executor: F5 BIG-IP with iControl REST and tmsh
- 6Deterministic executors: NetScaler NITRO, Radware Alteon and other load balancers (Anaya LB)
- 7Guardrails, approvals and audit for certificate changes
- 8Pre- and post-checks, rollback and the GitHub pipeline
- 9Capstone: end-to-end certificate renewal across the lab estate
