AWSControlTowerBP-BASELINE-CLOUDWATCH

1

Hello, Why AWSControlTowerBP-BASELINE-CLOUDWATCH stackset is in PENDING state for some of the accounts for about 4 months now? CT version is 3.1.

  • 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?

1개 답변
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 :)

George
답변함 일 년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠