Protected learning content

EasyFile Domain Setup and Production Launch

Confirming your learner account and course enrolment.

Capability outcome
Scope and safety boundary
What competence looks like
Launch principle
Before you begin
Module 1 - Domain ownership, governance and launch design
- 1.1 Map the accountable parties
- 1.2 Build a hostname register
- 1.3 Change design and TTL
Practical Lab 1 - Create the EasyFile launch control pack
Module 2 - DNS concepts and authoritative change control
- 2.1 DNS records answer different questions
- 2.2 Authoritative answer versus local observation
- 2.3 Avoid dangerous shortcuts
Module 3 - Domain verification and safe cutover
- 3.1 Verification proves control, not readiness
- 3.2 Sequence a cutover
- 3.3 Rollback must be executable
Practical Lab 2 - DNS verification and cutover simulation
Module 4 - TLS, browser security and edge controls
- 4.1 HTTPS is an end-to-end property
- 4.2 Security headers support but do not replace application controls
- 4.3 CORS is not an access-control system
Practical Lab 3 - Browser and API launch validation
Module 5 - Transactional email, sender identity and user trust
- 5.1 Email is part of the application perimeter
- 5.2 Authentication alignment
- 5.3 Safe verification links and messages
Module 6 - Release engineering and configuration safety
- 6.1 Separate configuration from code
- 6.2 Build once, promote with evidence
- 6.3 Health checks are meaningful only when they check something
Practical Lab 4 - Create a production release runbook
Module 7 - Observability, incident readiness and support
- 7.1 Observe the service from the user's path
- 7.2 Log safely
- 7.3 Incident response at launch
Module 8 - Operational acceptance and handover
- 8.1 Acceptance is a risk decision
- 8.2 Handover package
- 8.3 Continuous operations
Practical Lab 5 - Go/no-go simulation and tabletop incident
Capstone - EasyFile production launch dossier
- Required deliverables
Official reference set