AWS quicksuite documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in network connectivity context
Security assessment
Consistent branding update without technical security implications.
Diff
diff --git a/quicksuite/latest/userguide/vpc-amazon-virtual-private-cloud.md b/quicksuite/latest/userguide/vpc-amazon-virtual-private-cloud.md index 2f91c094b..9825b0e3b 100644 --- a//quicksuite/latest/userguide/vpc-amazon-virtual-private-cloud.md +++ b//quicksuite/latest/userguide/vpc-amazon-virtual-private-cloud.md @@ -26 +26 @@ If you have a default VPC and don't specify a subnet when you launch an instance -If you don't already have a VPC or want to use a new one, you can create one by following the instructions in [Getting started with Amazon VPC](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-getting-started.html) in the _Amazon VPC User Guide_. This section offers guidance on how to set up your VPC. The guidance includes options for public and private subnets and for AWS Site-to-Site VPN access for your corporate network (known as _on-premises access_). You can also use VPC peering or AWS Direct Connect to reach an on-premises database instance. +If you don't already have a VPC or want to use a new one, you can create one by following the instructions in [Getting started with Amazon VPC](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-getting-started.html) in the _Amazon VPC User Guide_. This section offers guidance on how to set up your VPC. The guidance includes options for public and private subnets and for AWS Site-to-Site VPN access for your corporate network (known as _on-premises access_). You can also use VPC peering or Direct Connect to reach an on-premises database instance.