BuildMidDevOpsAuto-graded
Put a multi-service stack behind nginx with TLS
Practical infrastructure skill: secure traffic, connections that stay open, and caching that never serves anyone stale content.Put a multi-service stack behind nginx: terminate TLS at the edge, redirect plain HTTP, route API traffic to one application and everything else to another, pass websocket upgrades through intact, and cache static assets sensibly. The applications themselves are fine — the configuration in front of them is what you are building.30 min
nginx
You're done when
- A TLS server block terminates HTTPS correctly.
- Plain HTTP requests are redirected to HTTPS.
- API paths route to the API application.
- Everything else routes to the second application by default.
- Websocket connections upgrade correctly, with the required headers passed through.
- Static assets are served with appropriate cache headers.
- Forwarded headers reach the applications, so they can see the original client and protocol.
What it measures
Transport layer securityTerminating TLS at the edge and redirecting cleanly, so no traffic stays on plain HTTP.
Performance measurement and benchmarkingChoosing cache headers that actually reduce load without serving stale assets.
Proxy correctnessGetting upgrade and forwarded headers right, the details that silently break websockets and client IP logging.
Your environment
Terminal + editorA full shell in the browser
Claude CodePre-authenticated, no key setup
Isolated microVMYours alone, wiped afterwards
Start this lab
30 min
Start labYou'll sign in to Anthropos to start. The lab opens in a private cloud workspace with Claude Code ready to use.AI Labs is part of Anthropos Workforce. Not on your plan yet? Book a demo