1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
0
Hey Meden,
you could check the following:
"a)" by checking if the AWSControlTowerExecution-role exists in that account and if not just create it manually. Then try again.
"b)", it looks like the role is still in use by the resource you censored. Analyze that resource, delete the controltower configuration in that resource and then try again.
If you are stuck, I would book a developer supportplan for 30$ for one month and let aws support analyze this issue from the backend in your case.
Sincerely Heiko
respondido hace un año
Contenido relevante
- preguntada hace un mes
- preguntada hace 2 meses
- preguntada hace un mes
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 3 años
- ¿Cómo puedo resolver el error “Failed to start the job flow due to an internal error” en Amazon EMR?OFICIAL DE AWSActualizada hace 3 meses
Hello Heiko,
I sincerely appreciate the prompt response. Fortunately, I resolved the situation by closing the account from the AWS organization utilizing the 'AWS::IAM::ServiceLinkedRole' with the identifier 'AWSServiceRoleForAWSControlTower'. However, I realized I might have overlooked properly deleting Amazon S3 Buckets in the Log Archive Account before closing the account. I assumed they would vanish after the 90-day account deletion deadline. If I'm mistaken, please correct me. Nonetheless, thank you for your guidance and the solution you provided.