AWS prescriptive-guidance documentation change
Summary
Reformatted FAQ questions with 'Q.' prefix and answers with 'A.' prefix. Removed a header line and made minor wording adjustments.
Security assessment
Changes are purely formatting and editorial improvements. No security vulnerabilities, configurations, or features are mentioned. GuardDuty reference remains unchanged advice.
Diff
diff --git a/prescriptive-guidance/latest/aws-control-tower/faq.md b/prescriptive-guidance/latest/aws-control-tower/faq.md index 1f196d0ef..daa7abd48 100644 --- a//prescriptive-guidance/latest/aws-control-tower/faq.md +++ b//prescriptive-guidance/latest/aws-control-tower/faq.md @@ -7,2 +6,0 @@ -Moving accounts from one OU to another?How does deployment of AWS Control Tower affect my Active Directory setup?How do I move Amazon GuardDuty to AWS Control Tower?Can I enroll the core accounts into AWS Control Tower?How do I get the pipeline build stage status to Succeeded? - @@ -11 +9 @@ Moving accounts from one OU to another?How does deployment of AWS Control Tower -## How can I move accounts from one organizational unit (OU) to another after it is enrolled in AWS Control Tower? +Q. How can I move accounts from one organizational unit (OU) to another after it is enrolled in AWS Control Tower? @@ -13 +11 @@ Moving accounts from one OU to another?How does deployment of AWS Control Tower -Update the provisioned product from AWS Service Catalog for the account, and in the parameters, select the destination OU. Also, do not move accounts manually from the AWS Organizations console, because that will create drift in AWS Control Tower. +A. Update the provisioned product from AWS Service Catalog for the account, and in the parameters, select the destination OU. Also, do not move accounts manually from the AWS Organizations console, because that will create drift in AWS Control Tower. @@ -15 +13 @@ Update the provisioned product from AWS Service Catalog for the account, and in -## I have an Active Directory setup in my AWS Landing Zone with a third-party provider. How does deployment of AWS Control Tower affect this? +Q. I have an Active Directory setup in my AWS Landing Zone with a third-party provider. How does deployment of AWS Control Tower affect this? @@ -17 +15 @@ Update the provisioned product from AWS Service Catalog for the account, and in -AWS Control Tower deployment will not interfere with your existing setup. The deployment will create only AWS Control Tower–specific permission sets. +A. AWS Control Tower deployment will not interfere with your existing setup. The deployment will create only AWS Control Tower-specific permission sets. @@ -19 +17 @@ AWS Control Tower deployment will not interfere with your existing setup. The de -## Amazon GuardDuty is activated in my AWS Landing Zone security account. How do I move that to AWS Control Tower +Q. Amazon GuardDuty is activated in my AWS Landing Zone security account. How do I move that to AWS Control Tower? @@ -21 +19 @@ AWS Control Tower deployment will not interfere with your existing setup. The de -You can use the newly created AWS Control Tower audit account to activate GuardDuty for your AWS Organizations organization. +A. You can use the newly created AWS Control Tower audit account to activate GuardDuty for your AWS Organizations organization. @@ -23 +21 @@ You can use the newly created AWS Control Tower audit account to activate GuardD -## Can I enroll the core accounts from AWS Landing Zone into AWS Control Tower? +Q. Can I enroll the core accounts from AWS Landing Zone into AWS Control Tower? @@ -25 +23 @@ You can use the newly created AWS Control Tower audit account to activate GuardD -Yes, you can enroll the core accounts, which are Shared-Services, Logging, and Security, with AWS Control Tower into any OU. +A. Yes, you can enroll the core accounts, which are Shared-Services, Logging, and Security, with AWS Control Tower into any OU. @@ -27 +25 @@ Yes, you can enroll the core accounts, which are Shared-Services, Logging, and S -## The AWS Landing Zone pipeline build stage status is **Failed**. How do I get it to the **Succeeded** status? +Q. The AWS Landing Zone pipeline build stage status is Failed. How do I get it to the Succeeded status? @@ -29 +27 @@ Yes, you can enroll the core accounts, which are Shared-Services, Logging, and S -If the build stage or Launch AVM stage failed, try adding `pip install --upgrade awscli` to the buildspec on line 24. +A. If the build stage or Launch AVM stage failed, try adding pip install --upgrade awscli to the buildspec on line 24.