AWS controltower documentation change
Summary
Removed deprecated Terraform Open Source transition instructions and streamlined Service Catalog integration content
Security assessment
The changes remove outdated product type transition guidance but do not reference security vulnerabilities or security feature updates. This is a documentation cleanup for deprecated processes.
Diff
diff --git a/controltower/latest/userguide/service-catalog.md b/controltower/latest/userguide/service-catalog.md index 7640b60a6..a15099506 100644 --- a//controltower/latest/userguide/service-catalog.md +++ b//controltower/latest/userguide/service-catalog.md @@ -5,2 +4,0 @@ -Transition to External product type - @@ -13,17 +11 @@ You can control the users that have access to specific products, which allows yo -In AWS Control Tower, your central cloud administrators and your end users can provision custom accounts in your landing zone using AWS Service Catalog products, called "custom blueprints". For more information, see [Step2. Create the AWS Service Catalog product](https://docs.aws.amazon.com/controltower/latest/userguide/afc-setup-steps.html#step-2-create-blueprint-product). - -AWS Control Tower also can make use of the Service Catalog APIs to further automate account provisioning and updating. For details, see [the AWS Service Catalog Developer Guide](https://docs.aws.amazon.com/servicecatalog/latest/dg/what-is-service-catalog.html). - -## Transition to the AWS Service Catalog External product type - -AWS Service Catalog changed support for _Terraform Open Source_ products and provisioned products to a new product type, called _External_. To learn more about this transition, review [Updating existing Terraform Open Source products and provisioned products to the External product type](https://docs.aws.amazon.com/servicecatalog/latest/adminguide/update_terraform_open_source_to_external.html) in the _AWS Service Catalog administrator guide_. - -This change effects existing accounts that you created or enrolled with AWS Control Tower account factory customization. To transition these accounts to the _External_ product type, you need to make changes in both AWS Service Catalog and AWS Control Tower. - -###### To transition to the External product type - - 1. Upgrade your existing Terraform Reference Engine for AWS Service Catalog to include support for both _External_ and _Terraform Open Source_ product types. For instructions about updating your Terraform Reference Engine, review the [AWS Service Catalog GitHub Repository](https://github.com/aws-samples/service-catalog-engine-for-terraform-os). - - 2. In AWS Service Catalog, duplicate any existing _Terraform Open Source_ products (blueprints), with the duplicates using the new _External_ product type. **Do not terminate the existing Terraform Open Source blueprints**. - - 3. In AWS Control Tower, update each account using a _Terraform Open Source_ blueprint to use the new _External_ blueprint. +In AWS Control Tower, your central cloud administrators and your end users can provision custom accounts in your landing zone using AWS Service Catalog products, called _custom blueprints_. For more information, see [Step2. Create the AWS Service Catalog product](https://docs.aws.amazon.com/controltower/latest/userguide/afc-setup-steps.html#step-2-create-blueprint-product). @@ -31 +13 @@ This change effects existing accounts that you created or enrolled with AWS Cont - 1. To update a blueprint, you must first remove the _Terraform Open Source_ blueprint completely. For more details, review [Remove a blueprint from an account](https://docs.aws.amazon.com/controltower/latest/userguide/remove-a-blueprint.html). +You can interact with AWS Control Tower accounts through the AWS Service Catalog console and APIs. For more information, see [Interact with AWS Control Tower accounts from AWS Service Catalog](./handle-accounts-with-service-catalog.html) @@ -33,14 +15 @@ This change effects existing accounts that you created or enrolled with AWS Cont - 2. Add the new _External_ blueprint to the same account. For more details, review [Add a blueprint to an AWS Control Tower account](https://docs.aws.amazon.com/controltower/latest/userguide/add-blueprint-to-account.html). - - 4. After all accounts using _Terraform Open Source_ blueprints are updated to _External_ blueprints, return to AWS Service Catalog and terminate any products that use _Terraform Open Source_ as the product type. - - 5. Going forward, all accounts created or enrolled using AWS Control Tower account factory customization must reference blueprints using the _AWS CloudFormation_ or _External_ product type. - -For blueprints created using the _External_ product type, AWS Control Tower only supports account customizations that use Terraform templates and the Terraform reference engine. To learn more, review [Set up for customization](https://docs.aws.amazon.com/controltower/latest/userguide/afc-setup-steps.html). - - - - -###### Note - -AWS Control Tower does not support _Terraform Open Source_ as a product type when creating new accounts. To learn more about these changes, review [Updating existing Terraform Open Source products and provisioned products to the _External_ product type](https://docs.aws.amazon.com/servicecatalog/latest/adminguide/update_terraform_open_source_to_external.html) in the _AWS Service Catalog administrator guide_. AWS Service Catalog will support customers through this product type transition, as needed. Contact your account representative to request assistance. +AWS Control Tower also can make use of the Service Catalog APIs to further automate account provisioning and updating. For details, see [the AWS Service Catalog Developer Guide](https://docs.aws.amazon.com/servicecatalog/latest/dg/what-is-service-catalog.html).