3 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
4
I resolved this issue by changing the KMS key policy, review this https://docs.aws.amazon.com/en_us/controltower/latest/userguide//configure-kms-keys.html#kms-key-policy-update
con risposta un anno fa
1
Hi There
I recommend performing the steps in Decommission Control Tower and manually removing resources. Specifically, check this section that outlines the resources that need to be manually removed before setting up CT again: https://docs.aws.amazon.com/controltower/latest/userguide/known-issues-decommissioning.html
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
This worked after I deleted AWSControlTowerBP-BASELINE-CLOUDTRAIL-MASTER stack.
This was the reason in my case since I have opted in for KMS for encryption