AWS evs documentation change
Summary
Clarified subnet configuration and route table associations for Amazon EVS environments, including service access subnet usage.
Security assessment
Changes provide clearer network setup instructions, which are operational best practices but do not directly address security issues or add security-specific documentation.
Diff
diff --git a/evs/latest/userguide/getting-started.md b/evs/latest/userguide/getting-started.md index 7bdacc533..6ca487dba 100644 --- a//evs/latest/userguide/getting-started.md +++ b//evs/latest/userguide/getting-started.md @@ -100 +100 @@ You must deploy in an AWS Region where Amazon EVS is supported. For more informa - 10. For **Number of private subnets** , choose **1**. + 10. For **Number of private subnets** , choose **1**. This private subnet will be used as the service access subnet that you provided to Amazon EVS during the environment creation step. For more information, see [Service access subnet](./concepts.html#concepts-service-access-subnet). @@ -135 +135 @@ During VPC creation, Amazon VPC automatically creates a main route table and imp -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 main route table to allow traffic to these systems. For more information about managing subnet route tables, see [Manage subnet route tables](https://docs.aws.amazon.com/vpc/latest/userguide/WorkWithRouteTables.html#Route_Replacing_Main_Table) in the _Amazon VPC User Guide_. +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 managing subnet route tables, see [Manage subnet route tables](https://docs.aws.amazon.com/vpc/latest/userguide/WorkWithRouteTables.html#Route_Replacing_Main_Table) in the _Amazon VPC User Guide_. @@ -137 +137 @@ Amazon EVS subnets are implicitly associated to your VPC’s main route table wh -After the Amazon EVS environment deploys, you can configure explicit route table associations to enable connectivity through a custom route table. For more information, see [Replace the main route table](https://docs.aws.amazon.com/vpc/latest/userguide/Route_Replacing_Main_Table.html) in the _Amazon VPC User Guide_. +After the Amazon EVS environment deploys, you can configure explicit route table associations to enable connectivity through a custom route table. For more information, see Explicitly associate Amazon EVS VLAN subnets to a VPC route table.