1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
In the meantime, I found the solution. It seems that with the ControlTower Cloudformation stacksets, the stackinstances remain in PENDING state (with the exception of a random one) after the ControlTower update. The solution is to update with overwriting having the same parameters as the initial stackset. All stackinstances will be in SUCCEDED state. I have to mention that this is only for having a clean report about failed, pending and succeded states of all stackinstances. Havin CT Cloudformation stackinstances in pending state will not affect in anyway the functionalities of CT. It sucks though :)
beantwortet vor einem Jahr
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
The same is with the: AWSControlTowerBP-BASELINE-CONFIG, AWSControlTowerBP-BASELINE-ROLES, AWSControlTowerBP-BASELINE-SERVICE-ROLES, AWSControlTowerBP-VPC-ACCOUNT-FACTORY-V1
for one of the accounts is SUCCEEDED state and for the others is in PENDING... Is this how CT works or is some bug?