AWS directoryservice documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' in production environment recommendations
Security assessment
Branding terminology change in existing security recommendation about private network access. The security guidance itself remains unchanged.
Diff
diff --git a/directoryservice/latest/admin-guide/microsoftadbasestep3.md b/directoryservice/latest/admin-guide/microsoftadbasestep3.md index a24251ebd..c9f8a4f15 100644 --- a//directoryservice/latest/admin-guide/microsoftadbasestep3.md +++ b//directoryservice/latest/admin-guide/microsoftadbasestep3.md @@ -9 +9 @@ Optional: Create a DHCP options set in AWS-DS-VPC01 for your directoryCreate a r -For this lab, we are using Amazon EC2 instances that have public IP addresses to make it easy to access the management instance from anywhere. In a production setting, you can use instances that are in a private VPC that are only accessible through a VPN or AWS Direct Connect link. There is no requirement the instance have a public IP address. +For this lab, we are using Amazon EC2 instances that have public IP addresses to make it easy to access the management instance from anywhere. In a production setting, you can use instances that are in a private VPC that are only accessible through a VPN or Direct Connect link. There is no requirement the instance have a public IP address.