From 5e93bd3e868757c11fb9b63d6d3ba1300f1a9d40 Mon Sep 17 00:00:00 2001 From: s-hadinger <49731213+s-hadinger@users.noreply.github.com> Date: Mon, 10 Jun 2019 16:45:14 +0200 Subject: [PATCH] Updated AWS IoT (markdown) --- AWS-IoT.md | 22 ++++++++++++++++++++-- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/AWS-IoT.md b/AWS-IoT.md index 9c1259f4..3483999f 100644 --- a/AWS-IoT.md +++ b/AWS-IoT.md @@ -309,12 +309,30 @@ Memory consumption (nominal): Note: if you use USE_WEBSERVER, your impact is lowered by 2k since the Web log buffer is reduced from 4k to 2k. Overall when activating USE_WEBSERVER, you just see a memory impact of 5.4k. -Memory needed during connection (TLS handshake): +Memory needed during connection (TLS handshake - fingerprint validation): -* ThunkStack = **4604 bytes** +* ThunkStack = **4608 bytes** * DecoderContext = **1152 bytes** * PrivateKey = **0** (stack if USE\_MQTT\_AWS\_IOT\_SKEY\_ON\_STACK) or 104 (heap) * Certificate = **0** (stack if USE\_MQTT\_AWS\_IOT\_SKEY\_ON\_STACK) or 1040 (heap) * Client Connect = **360 bytes** * **Total for connection = 6.1k** (or 7.3k if private key forced on heap) +Memory needed during connection (TLS handshake - full CA validation): + +* ThunkStack = **4608 bytes** +* CA Certificate in RAM = **328 bytes** +* DecoderContext = **3072 bytes** +* PrivateKey = **0** (stack if USE\_MQTT\_AWS\_IOT\_SKEY\_ON\_STACK) or 104 (heap) +* Certificate = **0** (stack if USE\_MQTT\_AWS\_IOT\_SKEY\_ON\_STACK) or 1040 (heap) +* Client Connect = **360 bytes** +* **Total for connection = 8.4k** (or 9.5k if private key forced on heap) + +### Connection Time + +ESP8266 is quite slow compared to modern processors when it comes to SSL handshake. Here are the observed performance to connect to an SSL/TLS server, depending on frequency (80MHz or 160MHz): + +AWS IoT Connection, with EC Private Key + +* **0.7s** at 160MHz +* **1.4s** at 80 MHz \ No newline at end of file