From 0a031a2ff05e928dbcbc04daff4e6aa6ae549935 Mon Sep 17 00:00:00 2001 From: Neil Hanlon Date: Tue, 15 Nov 2022 16:28:45 +0000 Subject: [PATCH] add some clarification on data flow for mirrormanager sop --- docs/sop/sop_mirrormanager2.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/sop/sop_mirrormanager2.md b/docs/sop/sop_mirrormanager2.md index 1ac951d..0be2cf7 100644 --- a/docs/sop/sop_mirrormanager2.md +++ b/docs/sop/sop_mirrormanager2.md @@ -57,6 +57,12 @@ If the backend of the CDN is down, it will attempt to guess what the user wanted Fastly -> www firewall -> mirrormanager server ``` +In reality, the flow is a lot more complex, and a diagram should be created to map it out in a more user-friendly manner (@TODO) + +``` +User -> Fastly -> AWS NLB over TLS, passthru -> www firewall cluster (decrypt TLS) -> mirrormanager server (Rocky CA TLS) +``` + ## Tasks Below are a list of possible tasks to take with mirror manager, depending on the scenario.