From e669b8f8def3c86530e8798260a36ad5bf4dec13 Mon Sep 17 00:00:00 2001
From: kazu634 <simoom634@yahoo.co.jp>
Date: Tue, 16 Apr 2019 17:26:38 +0700
Subject: [PATCH] Add work flow of using Route 53

---
 .../labs/infra/2019-04-14_how_to_use_Lego.md  | 25 +++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/content/labs/infra/2019-04-14_how_to_use_Lego.md b/content/labs/infra/2019-04-14_how_to_use_Lego.md
index 900a8ac..14398b4 100644
--- a/content/labs/infra/2019-04-14_how_to_use_Lego.md
+++ b/content/labs/infra/2019-04-14_how_to_use_Lego.md
@@ -177,6 +177,31 @@ Additional Configuration:
 - `AWS_HOSTED_ZONE_ID`
 - `AWS_REGION`
 
+つまりこのようなフローになります:
+
+<div class="mermaid">
+sequenceDiagram
+    participant User
+    participant Lego
+    participant Let’s Encrypt
+    participant Route53
+
+    note over User,Route53: Preparation
+    User ->> User: Specify AWS Environment Variables
+
+    note over User,Route53: Actual Operation
+    User ->> Lego: Request
+    Lego ->> Let’s Encrypt: Request
+    Let’s Encrypt ->> Lego: Return the key
+    Lego ->> Route53: Specify the key to the TXT record
+    note over Lego,Route53: Wait for TXT record to propagate
+    Lego ->> Let’s Encrypt: Request to continue
+    Let’s Encrypt ->> Route53: Check the TXT record
+    Route53 ->> Let’s Encrypt: Return the TXT record
+    Let’s Encrypt ->> Lego: SSL/TSL Certificate
+    Lego ->> User: SSL/TSL Certificate
+</div>
+
 ### AWS_ACCESS_KYE_IDとAWS_SECRET_ACCESS_KEYの調べ方
 後で書く