

# Walkthroughs
<a name="walkthroughs"></a>

This chapter contains walkthrough procedures that can help you in your use of AWS Control Tower.

**Topics**
+ [Walkthrough: Move from ALZ to AWS Control Tower](alz-to-control-tower.md)
+ [Walkthrough: Configure AWS Control Tower Without a VPC](configure-without-vpc.md)
+ [Remove AWS Control Tower resources](walkthrough-delete.md)
+ [Walkthrough: Set Up Security Groups in AWS Control Tower With AWS Firewall Manager](firewall-setup-walkthrough.md)
+ [Decommission an AWS Control Tower landing zone](decommission-landing-zone.md)

# Walkthrough: Move from ALZ to AWS Control Tower
<a name="alz-to-control-tower"></a>

Many AWS customers have adopted the [AWS Landing Zone solution (ALZ)](https://aws.amazon.com//solutions/implementations/aws-landing-zone/) to set up a secure, compliant, multi-account AWS environment. To reduce the burden of managing a landing zone, AWS created the managed service called AWS Control Tower.

No additional features are scheduled for ALZ; it is in long-term support only. Therefore, we recommend that you move to the AWS Control Tower service from ALZ. The blog that is linked in this chapter walks you through different considerations for that move, and it explains how you can plan a successful migration from ALZ to AWS Control Tower.

**Blog: **[Migrate AWS Landing Zone solution to AWS Control Tower](https://aws.amazon.com/blogs//mt/migrate-aws-landing-zone-solution-to-aws-control-tower/)

AWS Prescriptive Guidance offers more extensive documentation, including steps for transitioning from ALZ to AWS Control Tower. Essentially, you will enable AWS Control Tower governance in your existing organization that is running ALZ, based upon a number of prerequisites. For information, see [Transitioning from AWS Landing Zone to AWS Control Tower](https://docs.aws.amazon.com//prescriptive-guidance/latest/aws-control-tower/introduction.html).

# Walkthrough: Configure AWS Control Tower Without a VPC
<a name="configure-without-vpc"></a>

This topic walks through how to configure your AWS Control Tower accounts without a VPC.

If your workload does not require a VPC, you can do the following:
+ You can delete the AWS Control Tower virtual private cloud (VPC). This VPC was created when you set up your landing zone.
+ You can change your Account Factory settings so that new AWS Control Tower accounts are created without an associated VPC.

**Important**  
If you provision Account Factory accounts with VPC internet access settings enabled, that Account Factory setting overrides the control [Disallow internet access for an Amazon VPC instance managed by a customer](https://docs.aws.amazon.com//controltower/latest/userguide/data-residency-controls.html#disallow-vpc-internet-access). To avoid enabling internet access for newly provisioned accounts, you must change the setting in Account Factory.

## Delete the AWS Control Tower VPC
<a name="delete-master-vpc"></a>

Outside of AWS Control Tower, every AWS customer has a default VPC, which you can view on the Amazon Virtual Private Cloud (Amazon VPC) console at [https://console.aws.amazon.com/vpc/](https://console.aws.amazon.com/vpc/). You’ll recognize the default VPC, because its name always includes the word *(default)* at the end of the name.

When you set up a AWS Control Tower landing zone, AWS Control Tower deletes your AWS default VPC and creates a new AWS Control Tower default VPC. The new VPC is associated with your AWS Control Tower management account. This topic refers to that new VPC as the *Control Tower VPC*.

When you view your AWS Control Tower VPC in the Amazon VPC console, you will *not* see the word *(default)* at the end of the name. If you have more than one VPC, you must use the assigned CIDR range to identify the correct AWS Control Tower VPC.

You can delete the AWS Control Tower VPC, but if you later need a VPC in AWS Control Tower, you must create it yourself.

**To delete the AWS Control Tower VPC**

1. Open the Amazon VPC console at [https://console.aws.amazon.com/vpc/](https://console.aws.amazon.com/vpc/).

1. Search for **VPC** or select **VPC** from the Service Catalog options. You then see the **VPC Dashboard**.

1. From the menu on the left, choose **Your VPCs**. You then see a list of all your VPCs.

1. Identify the AWS Control Tower VPC by its CIDR range.

1. To delete the VPC, choose **Actions** and then choose **Delete VPC**.

An AWS *(default)* VPC already exists in every Region for the AWS Control Tower management account. To follow security best practices, if you choose to delete the AWS Control Tower VPC, it's best also to delete the AWS default VPC associated with the management account from all AWS Regions. Therefore, to secure the management account, remove the default VPC from each Region, as well as removing the VPC created by Control Tower in your AWS Control Tower home region.

## Optionally clean up the VPC resource in the account
<a name="remove-a-vpc"></a>

Optionally, to clean up the AWS Control Tower VPC resource, `aws-controltower-VPC`, from an existing account, you can remove the stack instance from the AWS CloudFormation StackSet `AWSControlTowerBP-VPC-ACCOUNT-FACTORY-V1`, after you make sure that there are no existing resources or resource dependencies in the VPC.

## Create an Account in AWS Control Tower Without a VPC
<a name="create-without-vpc"></a>

If your end-user workloads do not require VPCs, you can use this method to set up end-user accounts that don't have VPCs created for them automatically.

From the AWS Control Tower dashboard, you can view and edit your network configurations settings. After you change the settings so that AWS Control Tower accounts are created without an associated VPC, all new accounts are created without a VPC until you change the settings again.



**To configure Account Factory for creating accounts without VPCs**

1. Open a web browser, and navigate to the AWS Control Tower console at [https://console.aws.amazon.com/controltower](https://console.aws.amazon.com/controltower).

1. Choose **Account Factory** from the menu on the left.

1. You then see the Account Factory page with the **Network Configuration** section.

1. Note the current settings if you intend to restore them later.

1. Choose the **Edit** button in the **Network Configuration** section.

1.  In the **Edit account factory network configuration** page, go to the **VPC Configuration options for new accounts** section.

   You can follow **Option 1** or **Option 2**, or both, to ensure that AWS Control Tower does not create a VPC when provisioning an account.

   1. 

**Option 1 – Removing subnets**
      + Turn off the **Internet-accessible subnet** toggle switch.
      + Set the **Maximum number of private subnets** value to 0.

   1. 

**Option 2 – Removing AWS Regions**
      + Clear every checkbox in the **Regions for VPC creation** column.

1. Choose **Save**.

### Possible Errors
<a name="error-notes"></a>

Be aware of these possible errors that could occur when you delete your AWS Control Tower VPC or reconfigure Account Factory to create accounts without VPCs. 
+ Your existing management account may have dependencies or resources in the AWS Control Tower VPC, which can cause a *deletion failure* error. 
+ If you leave the default CIDR in place when setting up to launch new accounts without a VPC, your request fails with an error that *the CIDR is not valid*.

# Walkthrough: Set Up Security Groups in AWS Control Tower With AWS Firewall Manager
<a name="firewall-setup-walkthrough"></a>

The video shows you how to use the AWS Firewall Manager service to provide improvements to your network security for AWS Control Tower. You can designate a security administrator account that's enabled to set up security groups. You will see how you can configure security policies and enforce security rules for your AWS Control Tower organizations, and how you can remediate non-compliant resources by applying policies automatically. You can view the security groups that are in effect for each account and resource (such as an Amazon EC2 instance) in your organization.

You can create your own firewall policies, or you can subscribe to rules from trusted vendors.

## Set Up Security Groups With AWS Firewall Manager
<a name="firewall-manager-video"></a>

This video (8:02) describes how to set up better network infrastructure security for your resources and workloads in AWS Control Tower. For better viewing, select the icon at the lower right corner of the video to enlarge it to full screen. Captioning is available.

[![AWS Videos](http://img.youtube.com/vi/wocz0drq8-8/0.jpg)](http://www.youtube.com/watch?v=wocz0drq8-8)


For more information, see the [documentation on how to set up AWS WAF](https://docs.aws.amazon.com//waf/latest/developerguide/setting-up-waf.html).