AWS architecture-diagrams documentation change
Summary
Updated reference from 'AWS Direct Connect' to 'Direct Connect' in service link documentation
Security assessment
The change is a minor branding/text consistency update (removing 'AWS' prefix from a service name). No security implications are introduced or addressed, as the functionality of using Direct Connect (a private network connection) remains unchanged.
Diff
diff --git a/architecture-diagrams/latest/telecom-charging-ocs-chf-on-aws-outposts/telecom-charging-ocs-chf-on-aws-outposts.md b/architecture-diagrams/latest/telecom-charging-ocs-chf-on-aws-outposts/telecom-charging-ocs-chf-on-aws-outposts.md index 780555595..55da25a44 100644 --- a//architecture-diagrams/latest/telecom-charging-ocs-chf-on-aws-outposts/telecom-charging-ocs-chf-on-aws-outposts.md +++ b//architecture-diagrams/latest/telecom-charging-ocs-chf-on-aws-outposts/telecom-charging-ocs-chf-on-aws-outposts.md @@ -23 +23 @@ This architecture enables you to deploy a fully automated, resilient, low latenc - 4. A [service link](https://docs.aws.amazon.com/outposts/latest/userguide/how-outposts-works.html#how-service-link) connects the outpost to the home AWS Region. The service link is used for both management of **AWS Outposts** and intra-Virtual Private Cloud (VPC) traffic between the AWS Region and **AWS Outposts**. The service link can use the customer’s existing internet connection or **AWS Direct Connect**. + 4. A [service link](https://docs.aws.amazon.com/outposts/latest/userguide/how-outposts-works.html#how-service-link) connects the outpost to the home AWS Region. The service link is used for both management of **AWS Outposts** and intra-Virtual Private Cloud (VPC) traffic between the AWS Region and **AWS Outposts**. The service link can use the customer’s existing internet connection or **Direct Connect**.