AWS evs documentation change
Summary
Fixed typos in 'transit gateway' and 'on-premises' terminology, updated VPC route table section header, and clarified subnet association details
Security assessment
Changes are primarily typo corrections and documentation clarity improvements. The route table clarification helps prevent misconfigurations but does not directly address a specific security vulnerability or introduce new security features.
Diff
diff --git a/evs/latest/userguide/setting-up.md b/evs/latest/userguide/setting-up.md index 5e952be1f..3e20c1976 100644 --- a//evs/latest/userguide/setting-up.md +++ b//evs/latest/userguide/setting-up.md @@ -5 +5 @@ -Sign up for AWSCreate an IAM userCreate an IAM role to delegate Amazon EVS permission to an IAM userSign up for an AWS Business, AWS Enterprise On-Ramp, or AWS Enterprise Support planCheck quotasPlan VPC CIDR sizes and configure VPC componentsCreate VPC Route Server infrastructureCreate a transit gateway for on-premises connectivityCreate an Amazon EC2 Capacity ReservationSet up the AWS CLICreate an Amazon EC2 key pairPrepare your environment for VMware Cloud Foundation (VCF)Acquire VCF license keysVMware HCX prerequisites +Sign up for AWSCreate an IAM userCreate an IAM role to delegate Amazon EVS permission to an IAM userSign up for an AWS Business, AWS Enterprise On-Ramp, or AWS Enterprise Support planCheck quotasPlan VPC CIDR sizes and configure VPC componentsCreate VPC Route Server infrastructureCreate a transit gatway for on-premesis connectivityCreate an Amazon EC2 Capacity ReservationSet up the AWS CLICreate an Amazon EC2 key pairPrepare your environment for VMware Cloud Foundation (VCF)Acquire VCF license keysVMware HCX prerequisites @@ -31 +31 @@ To use Amazon EVS, you will need to configure other AWS services, as well as set - * Create a transit gateway for on-premises connectivity + * Create a transit gatway for on-premesis connectivity @@ -211 +211 @@ To enable Amazon EVS environment creation, you must provide Amazon EVS with a VP -### Main route table +### Configure the VPC main route table @@ -213 +213 @@ To enable Amazon EVS environment creation, you must provide Amazon EVS with a VP -Amazon EVS subnets are implicitly associated to your VPC’s main route table when they are created. To enable connectivity to dependent services such as DNS or on-premises systems for successful environment deployment, you must configure the VPC’s main route table to allow traffic to these systems. For more information about main route table configuration for Amazon EVS, see [Configure the VPC main route table](./getting-started.html#getting-started-vpc-main-route-table-config). +Amazon EVS VLAN subnets are implicitly associated to the VPC main route table. To enable connectivity to dependent services such as DNS or on-premises systems for successful environment deployment, you must configure the main route table to allow traffic to these systems. For more information about main route table configuration for Amazon EVS, see [Configure the VPC main route table](./getting-started.html#getting-started-vpc-main-route-table-config). @@ -245 +245 @@ Amazon EVS uses Amazon VPC Route Server to to enable BGP-based dynamic routing t -## Create a transit gateway for on-premises connectivity +## Create a transit gatway for on-premesis connectivity