AWS workspaces-web documentation change
Summary
Changed from Elastic IP allocation guide to VPC setup wizard instructions with subnet/NAT configuration
Security assessment
This is a procedural change shifting focus from Elastic IP management to VPC creation. While VPC configuration impacts network security, there's no evidence of addressing vulnerabilities or security incidents. The changes emphasize infrastructure setup rather than security controls.
Diff
diff --git a/workspaces-web/latest/adminguide/vpc-step1.md b/workspaces-web/latest/adminguide/vpc-step1.md index 267cfddec..bedd03f8a 100644 --- a//workspaces-web/latest/adminguide/vpc-step1.md +++ b//workspaces-web/latest/adminguide/vpc-step1.md @@ -5 +5 @@ -# Allocating an Elastic IP address +# Quick VPC Setup (1 minute) @@ -7 +7 @@ -Before you create your VPC, you must allocate an Elastic IP address in your WorkSpaces Secure Browser Region. Once allocated, you can associate the Elastic IP address with your NAT gateway. With an Elastic IP address, you can mask a failure of your streaming instance by rapidly remapping the address to another streaming instance in your VPC. For more information, see [Elastic IP addresses](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-eips.html). +Complete the following steps to quickly create a dedicated VPC for WorkSpaces Secure Browser with public and private subnets for internet access. If you want to use an existing VPC, see [VPC requirements for Amazon WorkSpaces Secure Browser](./vpc-reqs.html) to verify it meets the requirements. @@ -11 +11 @@ Before you create your VPC, you must allocate an Elastic IP address in your Work -Charges might apply to Elastic IP addresses that you use. For more information, see the [Elastic IP addresses pricing page](https://aws.amazon.com/ec2/pricing/on-demand/#Elastic_IP_Addresses). +Make sure you're in your desired AWS Region. You can change the region in the console if needed. @@ -13 +13 @@ Charges might apply to Elastic IP addresses that you use. For more information, -If you don't already have an Elastic IP address, complete the following steps. If you want to use an existing Elastic IP address, you must first verify that it isn't currently associated with another instance or network interface. +###### To quickly set up a VPC @@ -15 +15 @@ If you don't already have an Elastic IP address, complete the following steps. I -###### To allocate an Elastic IP address + 1. Open the VPC creation wizard: [Create VPC with resources](https://console.aws.amazon.com/vpcconsole/home#CreateVpc:createMode=vpcWithResources). Keep all settings as default unless specified below: @@ -17 +17 @@ If you don't already have an Elastic IP address, complete the following steps. I - 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). + * For **Resource to create** , select **VPC and more**. @@ -19 +19 @@ If you don't already have an Elastic IP address, complete the following steps. I - 2. In the navigation pane, under **Network & Security**, choose **Elastic IPs**. + * For **Name tag** , select **auto-generate** and enter a descriptive name for your VPC (e.g., `WSB-VPC`). @@ -21 +21 @@ If you don't already have an Elastic IP address, complete the following steps. I - 3. Choose **Allocate New Address** , and then choose **Allocate**. + * For **IPv4 CIDR block** , by default, the VPC uses `10.0.0.0/16`. You can specify a different IPv4 CIDR block if needed. @@ -23 +23 @@ If you don't already have an Elastic IP address, complete the following steps. I - 4. Note the Elastic IP address shown on the console. + * For **Tenancy** , select **Default** (VPCs with dedicated tenancy are not supported). @@ -25 +25 @@ If you don't already have an Elastic IP address, complete the following steps. I - 5. In the upper-right corner of the **Elastic IPs** pane, click the **×** icon to close the pane. + * For **Number of Availability Zones (AZs)** , select **2**. @@ -26,0 +27 @@ If you don't already have an Elastic IP address, complete the following steps. I + * Expand **Customize AZs** and select 2 different Availability Zones that are supported by WorkSpaces Secure Browser. For the list of supported AZs, see [Supported Availability Zones for Amazon WorkSpaces Secure Browser](./availability-zones.html). @@ -27,0 +29 @@ If you don't already have an Elastic IP address, complete the following steps. I + * For **Number of public subnets** , select **2**. @@ -28,0 +31,18 @@ If you don't already have an Elastic IP address, complete the following steps. I + * For **Number of private subnets** , select **2**. + + * For **Subnet CIDR blocks** , if you need to customize the CIDR blocks in your subnets, expand **Customize subnets CIDR blocks**. Ensure each subnet has sufficient IP addresses for your expected traffic. + + * For **NAT gateways** , select **Regional** to enable internet access for private subnets across all Availability Zones. + + * For **VPC endpoints** , select **None**. If you need direct S3 access without going through the NAT gateway, select **S3 Gateway**. + + * For **DNS options** , keep **DNS options** enabled (default) to ensure proper name resolution within your VPC. + + 2. Review the Preview pane, then choose **Create VPC**. + + + + +###### Note + +Additional charges apply for NAT gateways and VPC endpoints. For more information, see the [VPC pricing page](https://aws.amazon.com/vpc/pricing/). @@ -38 +58 @@ Creating a new VPC -New VPC +Subnet route tables