MODULE 03 · FDE ACADEMY
Deploy
A deployment is not a build that has been copied to a server. It is a system with a boundary, a way in, an owner and a record. This module is about the four things that turn the previous module’s stack into something a business can run.
- Lessons
- 5
- Module
- 03 of 5
The order is deliberate: serve, place, protect, observe. Each lesson has an artefact — a measured throughput figure, a boundary diagram, a proof that a removed user is removed, a retention rule — and together they are most of what a security review asks for.
Everything here is done against recipes on this site, so each step carries the documentation it came from and the architecture claims can be checked against the diagram rather than taken on trust.
- Covers
- cloudlocal LLMnetworkingauthenticationloggingmonitoring
Free and self-paced. No certification is offered.
Lessons
5 lessons
Each one ends with a task carried out somewhere on this site.
- 01Serve a model on hardware you choseFrom a sized model to a measured endpoint: throughput under concurrency, what happens at the queue, and the difference between a machine that fits the weights and one that serves the users.Half a day, most of it downloading weights and measuring.llm-inferencelinux5 steps
- 02Where it runs: the building, your tenancy, or a vendorThree solution classes and the ladder between them. Custody is not the same as control, and crossing into your own cloud account is still a crossing.About an hour of reading and comparison, no hardware needed.awsazurecompliance-governance5 steps
- 03Networking: who can reach thisA reverse proxy, TLS, one exposed port and a model server that is not on the internet. The unglamorous layer that decides whether a stack is a deployment or an incident.Two hours, plus however long the TLS material takes to obtain.networkingsecurity-hardeninglinux5 steps
- 04Authentication, and the leaving testSingle sign-on against the identity the customer already has, groups that map to what a person may retrieve, and the check that matters: someone leaves, and the deployment knows.Half a day if the customer’s identity provider is available to you.identity-ssosecurity-hardening5 steps
- 05Logging, monitoring, and the routine that uses themWhat to record and what not to, the five numbers worth watching, and the weekly routine that turns telemetry into something a customer can operate without you.Two hours to set up, then a recurring half-hour that is the point.mlopssecurity-hardeningllm-evaluation5 steps