From 07249b1288c70a3f63c56ae5094bab7b5db64744 Mon Sep 17 00:00:00 2001 From: Malte Poll Date: Tue, 10 Oct 2023 18:03:06 +0200 Subject: [PATCH] docs: add note about current AWS CVM issues (v2.12) --- .../version-2.12/getting-started/first-steps.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/versioned_docs/version-2.12/getting-started/first-steps.md b/docs/versioned_docs/version-2.12/getting-started/first-steps.md index 0b224e04da..07b7f84106 100644 --- a/docs/versioned_docs/version-2.12/getting-started/first-steps.md +++ b/docs/versioned_docs/version-2.12/getting-started/first-steps.md @@ -170,6 +170,20 @@ If you encounter any problem with the following steps, make sure to use the [lat ::: + :::note + + **AWS**: Currently, confidential VMs may temporarily fail to boot. + AWS is actively working on a solution. + If creating or initializing a cluster fails, terminate the cluster and try again later. + Alternatively, you can use non-confidential Nitro VMs for evaluation purposes. + To do so, generate a new configuration with the `aws-nitro-tpm` attestation variant: + + ```bash + constellation config generate aws --attestation aws-nitro-tpm + ``` + + ::: + 5. Configure kubectl. ```bash