From 62d1aee76ec3af987fc1d254d1758b35ca0fa347 Mon Sep 17 00:00:00 2001 From: amela Date: Thu, 25 Jul 2024 09:30:20 +0200 Subject: [PATCH] docs: Improve instructions for DCAP migration --- .../set-up-trusted-execution-environment-tee.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/node/run-your-node/prerequisites/set-up-trusted-execution-environment-tee.md b/docs/node/run-your-node/prerequisites/set-up-trusted-execution-environment-tee.md index a8de2f4ce8..c286157d37 100644 --- a/docs/node/run-your-node/prerequisites/set-up-trusted-execution-environment-tee.md +++ b/docs/node/run-your-node/prerequisites/set-up-trusted-execution-environment-tee.md @@ -292,8 +292,7 @@ operational. For transitioning to the DCAP attestation, follow these steps: 1. See if your system [supports DCAP attestation]. If your hardware does not support DCAP attestation, you'll need to migrate your node to newer hardware. -2. [Gracefully shutdown] your compute nodes (Sapphire and Cipher). -3. Transition to DCAP attestation: +2. Transition to DCAP attestation: - In case you are running AESM service on Docker follow [these instructions]. - Otherwise manually configure AESM service to use DCAP attestation: 1. Remove any leftover EPID attestation packages. If running on Ubuntu 22.04 run @@ -307,9 +306,9 @@ support DCAP attestation, you'll need to migrate your node to newer hardware. ```bash sudo systemctl restart aesmd.service ``` -4. [Configure the Quote Provider]. -5. Use the [attestation tool] to test if your settings are correct. -6. Start your compute node. +3. [Configure the Quote Provider]. +4. Use the [attestation tool] to test if your settings are correct. +5. Restart your compute node and verify that node is `ready`. [these instructions]: #dcap-attestation-docker [supports DCAP attestation]: #aesm-service