AWS directconnect documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in title and configuration example text
Security assessment
Branding terminology update without altering routing configuration guidance or security aspects of virtual interface management. The AS_PATH routing example remains technically unchanged.
Diff
diff --git a/directconnect/latest/UserGuide/private-transit-vif-example.md b/directconnect/latest/UserGuide/private-transit-vif-example.md index 325f27f04..4dd1e6690 100644 --- a//directconnect/latest/UserGuide/private-transit-vif-example.md +++ b//directconnect/latest/UserGuide/private-transit-vif-example.md @@ -5 +5 @@ -# AWS Direct Connect private virtual interface routing example +# Direct Connect private virtual interface routing example @@ -7 +7 @@ -Consider the configuration where the AWS Direct Connect location 1 home Region is the same as the VPC home Region. There is a redundant AWS Direct Connect location in a different Region There are two private VIFs (VIF A and VIF B) from AWS Direct Connect location 1 (us-east-1) to the Direct Connect gateway. There is one private VIF (VIF C) from AWS Direct Connect location (us-west-1) to the Direct Connect gateway. To have AWS route traffic over VIF B before VIF A, set the AS_PATH attribute of VIF B to be shorter than the VIF A AS_PATH attribute. +Consider the configuration where the Direct Connect location 1 home Region is the same as the VPC home Region. There is a redundant Direct Connect location in a different Region There are two private VIFs (VIF A and VIF B) from Direct Connect location 1 (us-east-1) to the Direct Connect gateway. There is one private VIF (VIF C) from Direct Connect location (us-west-1) to the Direct Connect gateway. To have AWS route traffic over VIF B before VIF A, set the AS_PATH attribute of VIF B to be shorter than the VIF A AS_PATH attribute.