- 最新
- 投票最多
- 评论最多
Hi, while it would be possible to do that. Adding Cloudformation to CfCT that creates accounts would not be recommended. CfCT is designed to be triggered by the Control Tower Account creation process. Lifecycle events will be emitted as the account is created, and those are received by CfCT. So you would effectively creating a bit of a loop if you were to request accounts through CfCT. It would look a bit like this {Update CfCT config} -> {Trigger CfCT execution} -> {Control Tower creates account} -> {Trigger CfCT execution}. The first CfCT execution in that path won't apply anything to the new account as it doesn't exist yet.
Having another pipeline or automation process that handles account requests would be a more recommended option. This makes the process modular and easier to change or troubleshoot. So you would have {Account Request Process} -> {Control Tower creates account} -> {CfCT then updates the Account or Landing Zone}. This should stop redundant executions.
相关内容
- AWS 官方已更新 1 年前