Snehal Bhurewar

@fjromerom currently AFT does not support change of secondary region after AFT has been deployed. I have gone ahead and created a backlog to potentially support this in future. As...

@allanmori thank you for reaching out. Is this consistently failing with retries too? I would recommend updating to latest AFT [v1.6.2](https://github.com/aws-ia/terraform-aws-control_tower_account_factory/releases/tag/1.6.2) as there have been multiple changes and bug fixes...

@allanmori The steps to update would depend on how AFT was deployed in the your Control Tower environment: - If the AFT repository was cloned and then deployed: - Update...

@allanmori the filter for `"type:CONTROL_TOWER_ACCOUNT"` is intended as AFT needs to look for Service provisioned catalog products which are Control Tower accounts. I suspect that there was a Service Catalog...

@saefty, thank you for the feedback and the details. I have created a backlog to address this use case.

@jarrod-lowe thank you for reaching out. Currently this behavior is as per design, however, we do have an existing backlog to support structured JSON as input to `custom_fields`

Thanks for the feature request @oliviergaumond, I've gone ahead and made a backlog to address this with the team.

@PeterBengtson thank you for the feature request. I have created a backlog to look into ways to reduce the overall network setup cost for AFT.

@jannyg thank you for reaching out. I suspect there could be certain network configuration in the environment causing this. However, I would recommend reaching out to AWS Premium support for...

@andy-townsend thank you for reaching out. I have created a backlog to address your documentation request. For importing an existing account under AFT management, it needs to be: * Part...