AWS migrationhub-refactor-spaces documentation change
Summary
Fixed a broken URL link by adding an extra slash in the VPC connectivity documentation
Security assessment
The change only corrects a URL formatting issue in documentation. There's no evidence of security vulnerability remediation or security feature addition.
Diff
diff --git a/migrationhub-refactor-spaces/latest/userguide/how-it-works.md b/migrationhub-refactor-spaces/latest/userguide/how-it-works.md index 488794a2d..c52c0a13f 100644 --- a//migrationhub-refactor-spaces/latest/userguide/how-it-works.md +++ b//migrationhub-refactor-spaces/latest/userguide/how-it-works.md @@ -32 +32 @@ For services with URL endpoints in a VPC, Refactor Spaces uses Transit Gateway t -You can create environments without a network bridge so that you can use your existing network infrastructure to bridge communications across multiple AWS accounts. When you create an application in an environment without a bridge, you must connect your network infrastructure to the application proxy to route traffic to service endpoints with private URLs. You can connect VPCs across accounts in several ways, including [VPC Peering](https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html), [Transit Gateway](https://docs.aws.amazon.com/vpc/latest/tgw/what-is-transit-gateway.html), or [AWS PrivateLink](./vpc-interface-endpoints.html). For more information, see the [Amazon VPC-to-Amazon VPC connectivity options](https://docs.aws.amazon.com/whitepapers/latest/aws-vpc-connectivity-options/amazon-vpc-to-amazon-vpc-connectivity-options.html) in the _Amazon Virtual Private Cloud Connectivity Options_ AWS whitepaper. +You can create environments without a network bridge so that you can use your existing network infrastructure to bridge communications across multiple AWS accounts. When you create an application in an environment without a bridge, you must connect your network infrastructure to the application proxy to route traffic to service endpoints with private URLs. You can connect VPCs across accounts in several ways, including [VPC Peering](https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html), [Transit Gateway](https://docs.aws.amazon.com/vpc/latest/tgw/what-is-transit-gateway.html), or [AWS PrivateLink](./vpc-interface-endpoints.html). For more information, see the [Amazon VPC-to-Amazon VPC connectivity options](https://docs.aws.amazon.com//whitepapers/latest/aws-vpc-connectivity-options/amazon-vpc-to-amazon-vpc-connectivity-options.html) in the _Amazon Virtual Private Cloud Connectivity Options_ AWS whitepaper.