Private corporate batches, live online cohorts and 1-on-1 mentoring in the integrated HashiCorp toolchain — Packer, Terraform, Vault, Consul and Nomad working as one workflow — taught by a practitioner who runs it in production.
20 years across DevOps, SRE and Security · 10,000+ engineers trained · Trained teams at JPMorgan Chase, Verizon, Nokia and the World Bank
Principal DevOps Engineer & Architect
Rajesh teaches the HashiCorp products as one workflow rather than five courses — Packer producing the artefact Terraform provisions, Terraform state and remote backends with locking as the operational spine, Vault issuing dynamic credentials that expire instead of static secrets that leak, Consul carrying service identity and mesh intentions, and Nomad scheduling workloads that authenticate to Vault by workload identity. Sessions concentrate on the joins where real estates break: state locking and drift, Vault seal and unseal automation with recovery keys, Consul gossip and WAN federation, and the auth-method and policy design that decides whether a machine can read a secret at all. Policy as code and CI-driven promotion run through every module.
Twenty years across DevOps, SRE and Security, in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe and others. He has trained engineers at JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus — more than 10,000 people personally. He teaches what he runs, not what he reads.
You are booked with a named engineer, and that is who turns up. Marketplaces and larger providers rotate whoever is free, so the person who sold you the agenda is rarely the person teaching it.
The same trainer is available for the next engagement, which matters when a team builds on what it learned last time.
Your batch is assigned a named trainer before it starts, and that is who teaches it. See the full faculty.
Engagements are matched on the tool, not the calendar. For HashiCorp that means a trainer who has run it in production — the integrated HashiCorp toolchain — Packer, Terraform, Vault, Consul and Nomad working as one workflow — rather than whoever is free that week. You are told who is teaching before you commit, and that person is on the discovery call that shapes the agenda.
Where a batch is large enough to need a second trainer, the pairing is declared up front. The lead trainer stays accountable for the syllabus and the assessment either way.
Principal DevOps Engineer & Architect
Twenty years across DevOps, SRE and Security in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe, IBM/Emptoris, Ness, MindTree and Accenture. He has trained more than 10,000 engineers personally, at organisations including JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus. He teaches what he runs, not what he reads.
Teams of 8–30
Custom agenda, your timezone, onsite or online, NDA-friendly.
Request a quoteIndividual engineers
A private instructor and a curriculum built around your goal.
₹99,999Individuals who want peers
Scheduled batch, max 8 to 10 hours of live instruction.
₹34,999A private batch starts with a discovery call. We look at the stack you actually run — the CI system, the cloud, the constraints — and map the agenda onto it, so examples use your topology rather than a generic one.
Delivery is onsite at your premises, live online, or hybrid, scheduled around your release calendar rather than ours. Batches run 8 to 30 engineers.
Every attendee leaves with recordings, slides, lab repositories and a completion certificate. You receive an attendance and assessment report. Invoicing supports PO and GST.
Talk to us about a private HashiCorp batchHashiCorp produces a family of infrastructure tools that are usually learned one at a time but are designed to work as a single workflow. Packer builds immutable machine and container images from a versioned template. Terraform provisions infrastructure from declarative HCL and tracks it in state, consuming those images. Consul provides service discovery, health checking, a key-value store and a service mesh with mutual TLS between workloads. Vault issues and manages secrets — static, dynamic, and short-lived — along with PKI certificates, encryption as a service and identity-based access. Nomad schedules and runs workloads across the machines Terraform created.
The common thread is more than a shared configuration language. Every HashiCorp tool is built around the same model: declare intent in HCL, let the tool reconcile reality against it, and derive authority from identity rather than from network position. That is why the products compose so tightly — Nomad jobs fetch secrets from Vault using workload identity, Vault can use Consul for storage and Consul can use Vault as its certificate authority, Consul-Terraform-Sync reacts to service catalog changes by running Terraform, and Terraform provisions and configures all of them.
Learning HashiCorp tools in isolation produces engineers who can write a Terraform module but cannot explain where the database password comes from at run time, or who can unseal Vault but not automate it. The integrated view — image build to provisioning to secrets to discovery to scheduling, with policy as code across all of it — is what a platform team actually has to design.
Terraform has become the default way infrastructure is described in most organisations, and Vault the default answer to the question of where secrets live once they are no longer in a file. That adoption has moved the hiring conversation past individual tools. Teams now advertise for platform engineers who can design the whole chain: how an image is built and hardened, how it is provisioned, how a workload proves who it is, how it obtains credentials that expire, and how services find each other.
Licensing has also forced the issue. The move from open source to the Business Source Licence, and the emergence of forks, means organisations must make deliberate decisions about which editions they run, what HCP-managed services are worth, and where the OpenTofu question applies. Those are architecture decisions that need someone who understands what the enterprise features actually do.
The recurring failure in real estates is at the joins, not inside the tools. State stored without locking, Vault deployed without a sealed-recovery plan, Consul mesh enabled without understanding intentions, Nomad running with hard-coded credentials — every one of those is a toolchain design problem rather than a product problem.
Why these tools fit together and what they assume about your environment. HCL as a shared language, the declare-and-reconcile model, identity as the basis of authority, and a concrete reference architecture showing the path from image build through provisioning, secrets, discovery and scheduling.
Topics: HCL syntax, expressions, functions and blocks across products · The declare-and-reconcile model each tool implements · Identity-based security instead of network-based trust · Reference architecture: Packer to Terraform to Vault to Consul to Nomad · Where each product's responsibility begins and ends · Editions, HCP-managed services and licensing considerations · Setting up a local toolchain for the rest of the course
Where the chain starts. Packer templates in HCL, builders for cloud and container targets, provisioners that install and harden, post-processors and manifests, and the versioning discipline that lets Terraform reference an exact image rather than "latest".
Topics: HCL2 templates: sources, builds, variables and locals · Builders for AWS, Azure, GCP, Docker and virtualisation platforms · Provisioners: shell, file, Ansible and inline hardening · Post-processors, manifests and artefact metadata · Parallel builds across multiple targets from one template · Image versioning, tagging and lifecycle policy · Handing image identifiers to Terraform through data sources or a registry · Testing images before they are published
Terraform taught around state rather than syntax. The plan and apply lifecycle, providers and resource addressing, remote backends with locking, module design and versioning, workspaces and environment separation, and the lifecycle meta-arguments that decide in-place update versus destroy-and-recreate.
Topics: Declarative versus imperative, and where Terraform sits among the alternatives · CLI workflow: init, validate, plan, apply, show, destroy, console · Plan and apply lifecycle, the dependency graph and refresh behaviour · State: what the file holds, remote backends (S3, azurerm, GCS, Artifactory), locking, state surgery · Providers, the registry, required_providers, versions and upgrade strategy · Resources, resource behaviour and argument references · Meta-arguments: depends_on, count, for_each, provider, lifecycle · Input variables, output values and locals — types, precedence and scope · Data sources, HCL operators and the function library: string, collection, numeric, encoding, filesystem, date, crypto, IP network, type conversion · Provisioners: file, local-exec, remote-exec, and why they are a last resort · Templates, workspaces and environment separation · Modules: composition, versioning, registry consumption, custom modules and publishing · Tagging strategy, troubleshooting with TF_LOG, and reading common errors · HCP Terraform run workflows and multi-provider configurations in CI/CD · Drift detection, import and refactoring with moved blocks
Vault as an operating system for secrets. Deployment and the seal model, auth methods that map real identities to policies, static and dynamic secrets engines, PKI for short-lived certificates, transit for encryption as a service, and the policy design that determines who can read what.
Topics: Architecture, storage backends, seal and unseal, auto-unseal · Initialisation, recovery keys and operational key custody · Auth methods: AppRole, Kubernetes, JWT/OIDC, cloud IAM, LDAP · Policies: path syntax, capabilities, templated policies and identity · Static secrets: KV v1 versus v2, versioning and metadata · Dynamic secrets: database, cloud and SSH engines with leases and TTLs · PKI engine, intermediate CAs and short-lived certificate issuance · Transit engine for encryption as a service and key rotation · Audit devices, lease management, revocation and namespaces · High availability, replication and disaster recovery posture
How services find each other and how traffic between them is secured. Agents, servers and the gossip protocol, the service catalog and health checks, DNS and API discovery interfaces, the key-value store, then Connect service mesh with sidecar proxies, intentions and mutual TLS.
Topics: Agents, servers, Raft consensus and the gossip protocol · Service registration, health checks and the catalog · Discovery via DNS and HTTP API, and prepared queries · Key-value store, sessions and consul-template · ACL system: tokens, policies, roles and bootstrapping · Connect service mesh: sidecar proxies, intentions, mutual TLS · Ingress, terminating and mesh gateways · WAN federation and multi-datacentre topologies · Consul-Terraform-Sync: catalog changes driving Terraform runs
Running things once the infrastructure exists. Nomad's architecture and scheduler, job specifications with groups and tasks, task drivers for containers and raw binaries, constraints and affinities, then the integrations that make it worth using alongside Consul and Vault.
Topics: Servers, clients, evaluations, allocations and the scheduling flow · Job specification: job, group, task, resources and networks · Task drivers: Docker, exec, java, and driver selection · Constraints, affinities, spread and datacenter targeting · Update strategies: rolling, canary, blue-green and auto-revert · Consul integration: service registration, health and mesh · Vault integration: workload identity and templated secrets · Batch, system and periodic job types · Autoscaling, resource sizing and bin-packing behaviour · When Nomad is the right choice against Kubernetes
The integration work that only appears once all the products are present. A single identity model across the chain, secrets injected at run time rather than baked into images, policy as code enforced in the pipeline, Boundary for human access, and the promotion path from commit to production.
Topics: One identity model: cloud IAM, Vault auth, Consul ACL, Nomad workload identity · Secret injection patterns: agent templating, sidecars, CSI, environment · Terraform and Vault together without leaking secrets into state · Policy as code: Sentinel and OPA against Terraform plans · Pipeline design: build, plan, policy check, approve, apply, verify · Boundary for identity-based human access to infrastructure · Bootstrapping and the chicken-and-egg problems in a fresh estate · Migration order when adopting the toolchain incrementally
The part that starts on day two. Sizing and high availability for each control plane, upgrades and version compatibility across the chain, backup and restore that has actually been tested, observability and the metrics that matter, and the failure drills every team should have rehearsed.
Topics: Sizing and high-availability topologies per product · Upgrade order and version compatibility across the toolchain · Backup and restore: Vault snapshots, Consul snapshots, Terraform state · Telemetry, metrics and dashboards for each control plane · Failure drills: Vault sealed, Consul quorum lost, state lock stuck · Certificate and key rotation without an outage · Cost, licensing and edition decisions revisited with real usage · Runbooks, on-call expectations and access review
We rebuild the agenda around the tools you actually run.
Request a custom agendaBuild a hardened image with Packer, publish it, and have Terraform pick it up by data source so no image identifier is ever hard-coded.
Migrate a project from local state to a locked remote backend, refactor into modules with moved blocks, and prove a clean plan at the end.
Replace a hard-coded database credential with a Vault dynamic secret, watch the lease expire, and handle renewal in the application path.
Put two services into the Consul mesh with mutual TLS, prove traffic flows, then block it with an intention and observe exactly where it fails.
Deploy a Nomad job with a canary update strategy, ship a deliberately broken version, and watch the scheduler revert it while traffic continues.
Take a service from Git commit through Packer build, policy-gated Terraform apply, Vault-issued credentials and Consul mesh onto Nomad, then break one link and recover.
Billed yearly at ₹9,996
Max 8 to 10 hours of live instruction
Full program, private instructor
8–30 engineers · custom agenda · onsite or online · PO and GST invoicing
Refunds. If we cancel or postpone a cohort, you get a full refund within 15 days. There is no money-back guarantee otherwise.
Terms. Course material remains licensed to the attendee. Read the terms.
Your data. We don't share it with third parties. Privacy policy.
Certificate of completion
I took Terraform training with the tutor named Mithilesh. I requested to tailor the course curriculum for my needs. He did an excellent job of showing me how to write the Terraform script per the instructions provided.
Very good training session. Well explained from the basics to the complex concepts. Also tried to cover practicals and demos within the 3 hour sessions. The learning content and videos are of a great deal of help.
Basics explanation was exemplary from Rajesh where he dealt with complicated topics to be simple. Great learning stuff personally for me.
Very detailed explanation and has lots of patience in attending the questionnaire. Thanks again for your wonderful sessions.
Good discussion, helped us to understand different tools in SRE.
Got good lab sessions which kept the new DevOps tool learnings to the point and it helped a lot in my career.
| What matters | YouTube + blogs | Generic online course | Freelance marketplace | DevOpsSchool |
|---|---|---|---|---|
| Named practitioner | No | Rarely | Varies per booking | Yes — same trainer each time |
| Production experience | Unknown | Unknown | Unverified | 20 years, named employers |
| Custom agenda | No | No | Sometimes | Built from your stack |
| Onsite delivery | No | No | Sometimes | Yes |
| Lab environment | None | Sandbox that expires | Varies | Your own cloud — skill goes with you |
| Assessment | None | Quiz | Rarely | Assignments + capstone per module |
| Per-attendee certificates | No | Sometimes | Rarely | Yes |
| Corporate invoicing | No | Limited | Varies | PO and GST |
| Post-training support | None | Forum, time-limited | None | Lifetime forum access |
Tell us the team, the stack and the timeline. You'll get a straight answer, not a sales sequence.
Talk to an advisorPrefer to call or email?
More ways to reach us on the contact page.