search

aws-solutions / aws-control-tower-customizations

The Customizations for AWS Control Tower solution combines AWS Control Tower and other highly-available, trusted AWS services to help customers more quickly set up a secure, multi-account AWS environment using AWS best practices.
https://docs.aws.amazon.com/controltower/latest/userguide/cfct-overview.html
Apache License 2.0
355 stars 205 forks source link

Add Existing deployed template to Pipeline #124

Open anupinder opened 2 years ago

anupinder commented 2 years ago

If there is existing templated deployed and bring it to pipeline only way is to remove that template and re add it to pipeline. Is there any workaround ? For certain templates, you cann't delete but at same time want to bring to pipeline.

balltrev commented 2 years ago

Hey @anupinder, just to make sure I've understood your feature request, are you looking to have CfCT "import/ingest" StackSets that you've provisioned external to CfCT?

anupinder commented 2 years ago

At the end of day, you want pipeline to emcompass all stacksets deployed. You described exactly what I am asking and as most organization have stackset and pipeline deployment, it is chaos in long run.

krishnamoorthyrajendran commented 1 year ago

Sir, This code is running but the control tower will not be able to create it.

anupinder commented 1 year ago

CfCt has hardcoded "CustomControlTower" keyword for stacksets it creates. If it allows other keywords then it won't try recreate stackset if existing template is added to manifest. Either through some parameter in manifest file or pipeline with default goes to "CustomControlTower".